Automated electrocardiogram interpretation system and methods for use therewith

ABSTRACT

An electrocardiogram (ECG) interpretation system is operable to receive a captured image of an ECG printout. A waveform detection function is performed on the captured image to determine a plurality of locations of a plurality of ECG waveforms in the captured image. A plurality of waveform images are generated by partitioning the captured image based on the plurality of locations, where each of the plurality of waveform images includes one of the plurality of ECG waveforms. A plurality of pseudo-raw ECG signal data is generated by performing a signal reconstruction function on each of the plurality of waveform images, where each of the plurality of pseudo-raw ECG signal data corresponds to one of the plurality of waveform images. Diagnosis data is generated by performing a diagnosing function on the plurality of pseudo-raw ECG signal data. The diagnosis data is transmitted to a client device for display via a display device.

CROSS REFERENCE TO RELATED APPLICATIONS

The present U.S. Utility Patent Application claims priority pursuant to 35 U.S.C. § 120 as a continuation of U.S. Utility application Ser. No. 16/408,672, entitled “ECG INTERPRETATION SYSTEM”, filed May 10, 2019, which claims priority pursuant to 35 U.S.C. § 119(e) to U.S. Provisional Application No. 62/770,334, entitled “LESION TRACKING SYSTEM”, filed Nov. 21, 2018, both of which are hereby incorporated herein by reference in their entirety and made part of the present U.S. Utility Patent Application for all purposes.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

INCORPORATION-BY-REFERENCE OF MATERIAL SUBMITTED ON A COMPACT DISC

Not applicable.

BACKGROUND Technical Field

This invention relates generally to medical imaging devices and knowledge-based systems used in conjunction with client/server network architectures.

Description of Related Art

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

FIG. 1 is a schematic block diagram of an embodiment of a medical scan processing system;

FIG. 2A is a schematic block diagram of a client device in accordance with various embodiments;

FIG. 2B is a schematic block diagram of one or more subsystems in accordance with various embodiments;

FIG. 3 is a schematic block diagram of a database storage system in accordance with various embodiments;

FIG. 4A is schematic block diagram of a medical scan entry in accordance with various embodiments;

FIG. 4B is a schematic block diagram of abnormality data in accordance with various embodiments;

FIG. 5A is a schematic block diagram of a user profile entry in accordance with various embodiments;

FIG. 5B is a schematic block diagram of a medical scan analysis function entry in accordance with various embodiments;

FIGS. 6A-6B are schematic block diagram of a medical scan diagnosing system in accordance with various embodiments;

FIG. 7A is a flowchart representation of an inference step in accordance with various embodiments;

FIG. 7B is a flowchart representation of a detection step in accordance with various embodiments;

FIGS. 8A-8F are schematic block diagrams of a medical picture archive integration system in accordance with various embodiments;

FIG. 9 is a flowchart representation of a method for execution by a medical picture archive integration system in accordance with various embodiments;

FIG. 10A is a schematic block diagram of a de-identification system in accordance with various embodiments;

FIG. 10B is an illustration of an example of anonymizing patient identifiers in image data of a medical scan in accordance with various embodiments;

FIG. 11 presents a flowchart illustrating a method for execution by a de-identification system in accordance with various embodiments;

FIG. 12A is a schematic block diagram of a ECG interpretation system in accordance with various embodiments;

FIG. 12B is a schematic block diagram of an ECG entry in accordance with various embodiments;

FIGS. 12C-12E present flowchart representations of performing steps of a ECG processing function in accordance with various embodiments;

FIG. 12F is a schematic block diagram of an ECG interpretation system in accordance with various embodiments;

FIGS. 13A-13E are illustrations of an example user interface displayed via a display device in accordance with various embodiments;

FIG. 14 presents a flowchart illustrating a method for execution by an ECG interpretation system in accordance with various embodiments;

FIG. 15A is a schematic block diagram of a captured image processing system in accordance with various embodiments;

FIGS. 15B-15C are illustrations of an example user interface displayed via a display device in accordance with various embodiments;

FIG. 16A is a schematic block diagram of a lesion tracking system in accordance with various embodiments;

FIG. 16B is an illustration of an example of a lesion diameter measurement in accordance with various embodiments;

FIG. 16C is a flowchart illustration of performing a lesion volume measurement function in accordance with various embodiments; and

FIG. 16D is an illustration of an example interface displayed by a display device in accordance with various embodiments.

DETAILED DESCRIPTION

The present U.S. Utility Patent Application is related to U.S. Utility application Ser. No. 15/627,644, entitled “MEDICAL SCAN ASSISTED REVIEW SYSTEM”, filed 20 Jun. 2017, which claims priority pursuant to 35 U.S.C. § 119(e) to U.S. Provisional Application No. 62/511,150, entitled “MEDICAL SCAN ASSISTED REVIEW SYSTEM AND METHODS”, filed 25 May 2017, both of which are hereby incorporated herein by reference in their entirety and made part of the present U.S. Utility Patent Application for all purposes.

FIG. 1 presents a medical scan processing system 100, which can include one or more medical scan subsystems 101 that communicate bidirectionally with one or more client devices 120 via a wired and/or wireless network 150. The medical scan subsystems 101 can include a medical scan assisted review system 102, medical scan report labeling system 104, a medical scan annotator system 106, a medical scan diagnosing system 108, a medical scan interface feature evaluator system 110, a medical scan image analysis system 112, a medical scan natural language analysis system 114, and/or a medical scan comparison system 116. Some or all of the subsystems 101 can utilize the same processing devices, memory devices, and/or network interfaces, for example, running on a same set of shared servers connected to network 150. Alternatively or in addition, some or all of the subsystems 101 be assigned their own processing devices, memory devices, and/or network interfaces, for example, running separately on different sets of servers connected to network 150. Some or all of the subsystems 101 can interact directly with each other, for example, where one subsystem's output is transmitted directly as input to another subsystem via network 150. Network 150 can include one or more wireless and/or wired communication systems; one or more non-public intranet systems and/or public internet systems; and/or one or more local area networks (LAN) and/or wide area networks (WAN).

The medical scan processing system 100 can further include a database storage system 140, which can include one or more servers, one or more memory devices of one or more subsystems 101, and/or one or more other memory devices connected to network 150. The database storage system 140 can store one or more shared databases and/or one or more files stored on one or more memory devices that include database entries as described herein. The shared databases and/or files can each be utilized by some or all of the subsystems of the medical scan processing system, allowing some or all of the subsystems and/or client devices to retrieve, edit, add, or delete entries to the one or more databases and/or files.

The one or more client devices 120 can each be associated with one or more users of one or more subsystems of the medical scan processing system. Some or all of the client devices can be associated with hospitals or other medical institutions and/or associated with medical professionals, employees, or other individual users for example, located at one or more of the medical institutions. Some of the client devices 120 can correspond to one or more administrators of one or more subsystems of the medical scan processing system, allowing administrators to manage, supervise, or override functions of one or more subsystems for which they are responsible.

Some or all of the subsystems 101 of the medical scan processing system 100 can include a server that presents a website for operation via a browser of client devices 120. Alternatively or in addition, each client device can store application data corresponding to some or all subsystems, for example, a subset of the subsystems that are relevant to the user in a memory of the client device, and a processor of the client device can display the interactive interface based on instructions in the interface data stored in memory. For example, the website presented by a subsystem can operate via the application. Some or all of the websites presented can correspond to multiple subsystems, for example, where the multiple subsystems share the server presenting the website. Furthermore, the network 150 can be configured for secure and/or authenticated communications between the medical scan subsystems 101, the client devices 120 and the database storage system 140 to protect the data stored in the database storage system and the data communicated between the medical scan subsystems 101, the client devices 120 and the database storage system 140 from unauthorized access.

The medical scan assisted review system 102 can be used to aid medical professionals or other users in diagnosing, triaging, classifying, ranking, and/or otherwise reviewing medical scans by presenting a medical scan for review by a user by transmitting medical scan data of a selected medical scan and/or interface feature data of selected interface features of to a client device 120 corresponding to a user of the medical scan assisted review system for display via a display device of the client device. The medical scan assisted review system 102 can generate scan review data for a medical scan based on user input to the interactive interface displayed by the display device in response to prompts to provide the scan review data, for example, where the prompts correspond to one or more interface features.

The medical scan assisted review system 102 can be operable to receive, via a network, a medical scan for review. Abnormality annotation data can be generated by identifying one or more of abnormalities in the medical scan by utilizing a computer vision model that is trained on a plurality of training medical scans. The abnormality annotation data can include location data and classification data for each of the plurality of abnormalities and/or data that facilitates the visualization of the abnormalities in the scan image data. Report data including text describing each of the plurality of abnormalities is generated based on the abnormality data. The visualization and the report data, which can collectively be displayed annotation data, can be transmitted to a client device. A display device associated with the client device can display the visualization in conjunction with the medical scan via an interactive interface, and the display device can further display the report data via the interactive interface.

In various embodiments, longitudinal data, such as one or more additional scans of longitudinal data 433 of the medical scan or of similar scans, can be displayed in conjunction with the medical scan automatically, or in response to the user electing to view longitudinal data via user input. For example, the medical scan assisted review system can retrieve a previous scan or a future scan for the patient from a patient database or from the medical scan database automatically or in response to the user electing to view past patient data. One or more previous scans can be displayed in one or more corresponding windows adjacent to the current medical scan. For example, the user can select a past scan from the longitudinal data for display. Alternatively or in addition, the user can elect longitudinal parameters such as amount of time elapsed, scan type, electing to select the most recent and/or least recent scan, electing to select a future scan, electing to select a scan at a date closest to the scan, or other criteria, and the medical scan assisted review system can automatically select a previous scan that compares most favorably to the longitudinal parameters. The selected additional scan can be displayed in an adjacent window alongside the current medical scan. In some embodiments, multiple additional scans will be selected and can be displayed in multiple adjacent windows.

In various embodiments, a first window displaying an image slice 412 of the medical scan and an adjacent second window displaying an image slice of a selected additional scan will display image slices 412 determined to correspond with the currently displayed slice 412 of the medical scan. As described with respect to selecting a slice of a selected similar medical scan for display, this can be achieved based on selecting the image slice with a matching slice number, based on automatically determining the image slice that most closely matches the anatomical region corresponding to the currently displayed slice of the current scan, and/or based on determining the slice in the previous scan with the most similar view of the abnormality as the currently displayed slice. The user can use a single scroll bar or other single user input indication to jump to a different image slice, and the multiple windows can simultaneously display the same numbered image slice, or can scroll or jump by the same number of slices if different slice numbers are initially displayed. In some embodiments, three or more adjacent windows corresponding to the medical scan and two or more additional scans are displayed, and can all be controlled with the single scroll bar in a similar fashion.

The medical scan assisted review system 102 can automatically detect previous states of the identified abnormalities based on the abnormality data, such as the abnormality location data. The detected previous states of the identified abnormality can be circled, highlighted, or otherwise indicated in their corresponding window. The medical scan assisted review system 102 can retrieve classification data for the previous state of the abnormality by retrieving abnormality annotation data 442 of the similar abnormality mapped to the previous scan from the medical scan database 342. This data may not be assigned to the previous scan, and the medical scan assisted review system can automatically determine classification or other diagnosis data for the previous medical scan by utilizing the medical scan image analysis system as discussed. Alternatively or in addition, some or all of the abnormality classification data 445 or other diagnosis data 440 for the previous scan can be assigned values determined based on the abnormality classification data or other diagnosis data determined for the current scan. Such abnormality classification data 445 or other diagnosis data 440 determined for the previous scan can be mapped to the previous scan, and or mapped to the longitudinal data 433, in the database and/or transmitted to a responsible entity via the network.

The medical assisted review system can automatically generate state change data such as a change in size, volume, malignancy, or other changes to various classifiers of the abnormality. This can be achieved by automatically comparing image data of one or more previous scans and the current scan and/or by comparing abnormality data of the previous scan to abnormality data of the current scan. In some embodiments, such metrics can be calculated by utilizing the medical scan similarity analysis function, for example, where the output of the medical scan similarity analysis function such as the similarity score indicates distance, error, or other measured discrepancy in one or more abnormality classifier categories 444 and/or abnormality pattern categories 446. This calculated distance, error, or other measured discrepancy in each category can be used to quantify state change data, indicate a new classifier in one or more categories, to determine if a certain category has become more or less severe, or otherwise determine how the abnormality has changed over time. In various embodiments, this data can be displayed in one window, for example, where an increase in abnormality size is indicated by overlaying or highlighting an outline of the current abnormality over the corresponding image slice of the previous abnormality, or vice versa. In various embodiments where several past scans are available, such state change data can be determined over time, and statistical data showing growth rate changes over time or malignancy changes over time can be generated, for example, indicating if a growth rate is lessening or worsening over time. Image slices corresponding to multiple past scans can be displayed in sequence, for example, where a first scroll bar allows a user to scroll between image slice numbers, and a second scroll bar allows a user to scroll between the same image slice over time. In various embodiments the abnormality data, heat map data, or other interface features will be displayed in conjunction with the image slices of the past image data.

The medical scan report labeling system 104 can be used to automatically assign medical codes to medical scans based on user identified keywords, phrases, or other relevant medical condition terms of natural text data in a medical scan report of the medical scan, identified by users of the medical scan report labeling system 104. The medical scan report labeling system 104 can be operable to transmit a medical report that includes natural language text to a first client device for display. Identified medical condition term data can be received from the first client device in response. An alias mapping pair in a medical label alias database can be identified by determining that a medical condition term of the alias mapping pair compares favorably to the identified medical condition term data. A medical code that corresponds to the alias mapping pair and a medical scan that corresponds to the medical report can be transmitted to a second client device of an expert user for display, and accuracy data can be received from the second client device in response. The medical code is mapped to the first medical scan in a medical scan database when the accuracy data indicates that the medical code compares favorably to the medical scan.

The medical scan annotator system 106 can be used to gather annotations of medical scans based on review of the medical scan image data by users of the system such as radiologists or other medical professionals. Medical scans that require annotation, for example, that have been triaged from a hospital or other triaging entity, can be sent to multiple users selected by the medical scan annotator system 106, and the annotations received from the multiple medical professionals can be processed automatically by a processing system of the medical scan annotator system, allowing the medical scan annotator system to automatically determine a consensus annotation of each medical scan. Furthermore, the users can be automatically scored by the medical scan annotator system based on how closely their annotation matches to the consensus annotation or some other truth annotation, for example, corresponding to annotations of the medical scan assigned a truth flag. Users can be assigned automatically to annotate subsequent incoming medical scans based on their overall scores and/or based on categorized scores that correspond to an identified category of the incoming medical scan.

The medical scan annotator system 106 can be operable to select a medical scan for transmission via a network to a first client device and a second client device for display via an interactive interface, and annotation data can be received from the first client device and the second client device in response. Annotation similarity data can be generated by comparing the first annotation data to the second annotation data, and consensus annotation data can be generated based on the first annotation data and the second annotation data in response to the annotation similarity data indicating that the difference between the first annotation data and the second annotation data compares favorably to an annotation discrepancy threshold. The consensus annotation data can be mapped to the medical scan in a medical scan database.

A medical scan diagnosing system 108 can be used by hospitals, medical professionals, or other medical entities to automatically produce inference data for given medical scans by utilizing computer vision techniques and/or natural language processing techniques. This automatically generated inference data can be used to generate and/or update diagnosis data or other corresponding data of corresponding medical scan entries in a medical scan database. The medical scan diagnosing system can utilize a medical scan database, user database, and/or a medical scan analysis function database by communicating with the database storage system 140 via the network 150, and/or can utilize another medical scan database, user database, and/or function database stored in local memory.

The medical scan diagnosing system 108 can be operable to receive a medical scan. Diagnosis data of the medical scan can be generated by performing a medical scan inference function on the medical scan. The first medical scan can be transmitted to a first client device associated with a user of the medical scan diagnosing system in response to the diagnosis data indicating that the medical scan corresponds to a non-normal diagnosis. The medical scan can be displayed to the user via an interactive interface displayed by a display device corresponding to the first client device. Review data can be received from the first client device, where the review data is generated by the first client device in response to a prompt via the interactive interface. Updated diagnosis data can be generated based on the review data. The updated diagnosis data can be transmitted to a second client device associated with a requesting entity.

A medical scan interface feature evaluating system 110 can be used evaluate proposed interface features or currently used interface features of an interactive interface to present medical scans for review by medical professionals or other users of one or more subsystems 101. The medical scan interface feature evaluator system 110 can be operable to generate an ordered image-to-prompt mapping by selecting a set of user interface features to be displayed with each of an ordered set of medical scans. The set of medical scans and the ordered image-to-prompt mapping can be transmitted to a set of client devices. A set of responses can be generated by each client device in response to sequentially displaying each of the set of medical scans in conjunction with a mapped user interface feature indicated in the ordered image-to-prompt mapping via a user interface. Response score data can be generated by comparing each response to truth annotation data of the corresponding medical scan. Interface feature score data corresponding to each user interface feature can be generated based on aggregating the response score data, and is used to generate a ranking of the set of user interface features.

A medical scan image analysis system 112 can be used to generate and/or perform one or more medical scan image analysis functions by utilizing a computer vision-based learning algorithm 1350 on a training set of medical scans with known annotation data, diagnosis data, labeling and/or medical code data, report data, patient history data, patient risk factor data, and/or other metadata associated with medical scans. These medical scan image analysis functions can be used to generate inference data for new medical scans that are triaged or otherwise require inferred annotation data, diagnosis data, labeling and/or medical code data, and/or report data. For example, some medical scan image analysis functions can correspond to medical scan inference functions of the medical scan diagnosing system or other medical scan analysis functions of a medical scan analysis function database. The medical scan image analysis functions can be used to determine whether or not a medical scan is normal, to detect the location of an abnormality in one or more slices of a medical scan, and/or to characterize a detected abnormality. The medical scan image analysis system can be used to generate and/or perform computer vision based medical scan image analysis functions utilized by other subsystems of the medical scan processing system as described herein, aiding medical professionals to diagnose patients and/or to generate further data and models to characterize medical scans. The medical scan image analysis system can include a processing system that includes a processor and a memory that stores executable instructions that, when executed by the processing system, facilitate performance of operations.

The medical scan image analysis system 112 can be operable to receive a plurality of medical scans that represent a three-dimensional anatomical region and include a plurality of cross-sectional image slices. A plurality of three-dimensional subregions corresponding to each of the plurality of medical scans can be generated by selecting a proper subset of the plurality of cross-sectional image slices from each medical scan, and by further selecting a two-dimensional subregion from each proper subset of cross-sectional image slices. A learning algorithm can be performed on the plurality of three-dimensional subregions to generate a neural network. Inference data corresponding to a new medical scan received via the network can be generated by performing an inference algorithm on the new medical scan by utilizing the neural network. An inferred abnormality can be identified in the new medical scan based on the inference data.

The medical scan natural language analysis system 114 can determine a training set of medical scans with medical codes determined to be truth data. Corresponding medical reports and/or other natural language text data associated with a medical scan can be utilized to train a medical scan natural language analysis function by generating a medical report natural language model. The medical scan natural language analysis function can be utilized to generate inference data for incoming medical reports for other medical scans to automatically determine corresponding medical codes, which can be mapped to corresponding medical scans. Medical codes assigned to medical scans by utilizing the medical report natural language model can be utilized by other subsystems, for example, to train other medical scan analysis functions, to be used as truth data to verify annotations provided via other subsystems, to aid in diagnosis, or otherwise be used by other subsystems as described herein.

A medical scan comparison system 116 can be utilized by one or more subsystems to identify and/or display similar medical scans, for example, to perform or determine function parameters for a medical scan similarity analysis function, to generate or retrieve similar scan data, or otherwise compare medical scan data. The medical scan comparison system 116 can also utilize some or all features of other subsystems as described herein. The medical scan comparison system 116 can be operable to receive a medical scan via a network and can generate similar scan data. The similar scan data can include a subset of medical scans from a medical scan database and can be generated by performing an abnormality similarity function, such as medical scan similarity analysis function, to determine that a set of abnormalities included in the subset of medical scans compare favorably to an abnormality identified in the medical scan. At least one cross-sectional image can be selected from each medical scan of the subset of medical scans for display on a display device associated with a user of the medical scan comparison system in conjunction with the medical scan.

FIG. 2A presents an embodiment of client device 120. Each client device 120 can include one or more client processing devices 230, one or more client memory devices 240, one or more client input devices 250, one or more client network interfaces 260 operable to more support one or more communication links via the network 150 indirectly and/or directly, and/or one or more client display devices 270, connected via bus 280. Client applications 202, 204, 206, 208, 210, 212, 214, and/or 216 correspond to subsystems 102, 104, 106, 108, 110, 112, 114, and/or 116 of the medical scan processing system respectfully. Each client device 120 can receive the application data from the corresponding subsystem via network 150 by utilizing network interface 260, for storage in the one or more memory devices 240. In various embodiments, some or all client devices 120 can include a computing device associated with a radiologist, medical entity, or other user of one or more subsystems as described herein.

The one or more processing devices 230 can display interactive interface 275 on the one or more client display devices 270 in accordance with one or more of the client applications 202, 204, 206, 208, 210, 212, 214, and/or 216, for example, where a different interactive interface 275 is displayed for some or all of the client applications in accordance with the website presented by the corresponding subsystem 102, 104, 106, 108, 110, 112, 114 and/or 116. The user can provide input in response to menu data or other prompts presented by the interactive interface via the one or more client input devices 250, which can include a microphone, mouse, keyboard, touchscreen of display device 270 itself or other touchscreen, and/or other device allowing the user to interact with the interactive interface. The one or more processing devices 230 can process the input data and/or send raw or processed input data to the corresponding subsystem, and/or can receive and/or generate new data in response for presentation via the interactive interface 275 accordingly, by utilizing network interface 260 to communicate bidirectionally with one or more subsystems and/or databases of the medical scan processing system via network 150.

FIG. 2B presents an embodiment of a subsystem 101, which can be utilized in conjunction with subsystem 102, 104, 106, 108, 110, 112, 114 and/or 116. Each subsystem 101 can include one or more subsystem processing devices 235, one or more subsystem memory devices 245, and/or one or more subsystem network interfaces 265, connected via bus 285. The subsystem memory devices 245 can store executable instructions that, when executed by the one or more subsystem processing devices 235, facilitate performance of operations by the subsystem 101, as described for each subsystem herein.

FIG. 3 presents an embodiment of the database storage system 140. Database storage system 140 can include at least one database processing device 330, at least one database memory device 340, and at least one database network interface 360, operable to more support one or more communication links via the network 150 indirectly and/or directly, all connected via bus 380. The database storage system 140 can store one or more databases the at least one memory 340, which can include a medical scan database 342 that includes a plurality medical scan entries 352, a user database 344 that includes a plurality of user profile entries 354, a medical scan analysis function database 346 that includes a plurality of medical scan analysis function entries 356, an interface feature database 348 can include a plurality of interface feature entries 358, and/or other databases that store data generated and/or utilized by the subsystems 101. Some or all of the databases 342, 344, 346 and/or 348 can consist of multiple databases, can be stored relationally or non-relationally, and can include different types of entries and different mappings than those described herein. A database entry can include an entry in a relational table or entry in a non-relational structure. Some or all of the data attributes of an entry 352, 354, 356, and/or 358 can refer to data included in the entry itself or that is otherwise mapped to an identifier included in the entry and can be retrieved from, added to, modified, or deleted from the database storage system 140 based on a given identifier of the entry. Some or all of the databases 342, 344, 346, and/or 348 can instead be stored locally by a corresponding subsystem, for example, if they are utilized by only one subsystem.

The processing device 330 can facilitate read/write requests received from subsystems and/or client devices via the network 150 based on read/write permissions for each database stored in the at least one memory device 340. Different subsystems can be assigned different read/write permissions for each database based on the functions of the subsystem, and different client devices 120 can be assigned different read/write permissions for each database. One or more client devices 120 can correspond to one or more administrators of one or more of the databases stored by the database storage system, and database administrator devices can manage one or more assigned databases, supervise assess and/or efficiency, edit permissions, or otherwise oversee database processes based on input to the client device via interactive interface 275.

FIG. 4A presents an embodiment of a medical scan entry 352, stored in medical scan database 342, included in metadata of a medical scan, and/or otherwise associated with a medical scan. A medical scan can include imaging data corresponding to a CT scan, x-ray, MRI, PET scan, Ultrasound, EEG, mammogram, or other type of radiological scan or medical scan taken of an anatomical region of a human body, animal, organism, or object and further can include metadata corresponding to the imaging data. Some or all of the medical scan entries can be formatted in accordance with a Digital Imaging and Communications in Medicine (DICOM) format or other standardized image format, and some or more of the fields of the medical scan entry 352 can be included in a DICOM header or other standardized header of the medical scan. Medical scans can be awaiting review or can have already been reviewed by one or more users or automatic processes and can include tentative diagnosis data automatically generated by a subsystem, generated based on user input, and/or generated from another source. Some medical scans can include final, known diagnosis data generated by a subsystem and/or generated based on user input, and/or generated from another source, and can included in training sets used to train processes used by one or more subsystems such as the medical scan image analysis system 112 and/or the medical scan natural language analysis system 114.

Some medical scans can include one or more abnormalities, which can be identified by a user or can be identified automatically. Abnormalities can include nodules, for example malignant nodules identified in a chest CT scan. Abnormalities can also include and/or be characterized by one or more abnormality pattern categories such as such as cardiomegaly, consolidation, effusion, emphysema, and/or fracture, for example identified in a chest x-ray. Abnormalities can also include any other unknown, malignant or benign feature of a medical scan identified as not normal. Some scans can contain zero abnormalities, and can be identified as normal scans. Some scans identified as normal scans can include identified abnormalities that are classified as benign, and include zero abnormalities classified as either unknown or malignant. Scans identified as normal scans may include abnormalities that were not detected by one or more subsystems and/or by an originating entity. Thus, some scans may be improperly identified as normal. Similarly, scans identified to include at least one abnormality may include at least one abnormality that was improperly detected as an abnormality by one or more subsystems and/or by an originating entity. Thus, some scans may be improperly identified as containing abnormalities.

Each medical scan entry 352 can be identified by its own medical scan identifier 353, and can include or otherwise map to medical scan image data 410, and metadata such as scan classifier data 420, patient history data 430, diagnosis data 440, annotation author data 450, confidence score data 460, display parameter data 470, similar scan data 480, training set data 490, and/or other data relating to the medical scan. Some or all of the data included in a medical scan entry 352 can be used to aid a user in generating or editing diagnosis data 440, for example, in conjunction with the medical scan assisted review system 102, the medical scan report labeling system 104, and/or the medical scan annotator system 106. Some or all of the data included in a medical scan entry 352 can be used to allow one or more subsystems 101, such as automated portions of the medical scan report labeling system 104 and/or the medical scan diagnosing system 108, to automatically generate and/or edit diagnosis data 440 or other data the medical scan. Some or all of the data included in a medical scan entry 352 can be used to train some or all medical scan analysis functions of the medical scan analysis function database 346 such as one or more medical scan image analysis functions, one or more medical scan natural language analysis functions, one or more medical scan similarity analysis functions, one or more medical report generator functions, and/or one or more medical report analysis functions, for example, in conjunction with the medical scan image analysis system 112, the medical scan natural language analysis system 114, and/or the medical scan comparison system 116.

The medical scan entries 352 and the associated data as described herein can also refer to data associated with a medical scan that is not stored by the medical scan database, for example, that is uploaded by a client device for direct transmission to a subsystem, data generated by a subsystem and used as input to another subsystem or transmitted directly to a client device, data stored by a Picture Archive and Communication System (PACS) communicating with the medical scan processing system 100, or other data associated with a medical scan that is received and or generated without being stored in the medical scan database 342. For example, some or all of the structure and data attributes described with respect to a medical scan entry 352 can also correspond to structure and/or data attribute of data objects or other data generated by and/or transmitted between subsystems and/or client devices that correspond to a medical scan. Herein, any of the data attributes described with respect to a medical scan entry 352 can also correspond to data extracted from a data object generated by a subsystem or client device or data otherwise received from a subsystem, client device, or other source via network 150 that corresponds to a medical scan.

The medical scan image data 410 can include one or more images corresponding to a medical scan. The medical scan image data 410 can include one or more image slices 412, for example, corresponding to a single x-ray image, a plurality of cross-sectional, tomographic images of a scan such as a CT scan, or any plurality of images taken from the same or different point at the same or different angles. The medical scan image data 410 can also indicate an ordering of the one or more image slices 412. Herein, a “medical scan” can refer a full scan of any type represented by medical scan image data 410. Herein, an “image slice” can refer to one of a plurality of cross-sectional images of the medical scan image data 410, one of a plurality of images taken from different angles of the medical scan image data 410, and/or the single image of the medical scan image data 410 that includes only one image. Furthermore “plurality of image slices” can refer to all of the images of the associated medical scan, and refers to only a single image if the medical scan image data 410 includes only one image. Each image slice 412 can include a plurality of pixel values 414 mapped to each pixel of the image slice. Each pixel value can correspond to a density value, such as a Hounsfield value or other measure of density. Pixel values can also correspond to a grayscale value, a RGB (Red-Green-Blue) or other color value, or other data stored by each pixel of an image slice 412.

Scan classifier data 420 can indicate classifying data of the medical scan. Scan classifier data can include scan type data 421, for example, indicating the modality of the scan. The scan classifier data can indicate that the scan is a CT scan, x-ray, Mill, PET scan, Ultrasound, EEG, mammogram, or other type of scan. Scan classifier data 420 can also include anatomical region data 422, indicating for example, the scan is a scan of the chest, head, right knee, or other anatomical region. Scan classifier data can also include originating entity data 423, indicating the hospital where the scan was taken and/or a user that uploaded the scan to the system. If the originating entity data corresponds to a user of one or more subsystems 101, the originating entity data can include a corresponding user profile identifier and/or include other data from the user profile entry 354 of the user. Scan classifier data 420 can include geographic region data 424, indicating a city, state, and/or country from which the scan originated, for example, based on the user data retrieved from the user database 344 based on the originating entity. Scan classifier data can also include machine data 425, which can include machine identifier data, machine model data, machine calibration data, and/or contrast agent data, for example based on imaging machine data retrieved from the user database 344 based on the originating entity data 423. The scan classifier data 420 can include scan date data 426 indicating when the scan was taken. The scan classifier data 420 can include scan priority data 427, which can indicate a priority score, ranking, number in a queue, or other priority data with regard to triaging and/or review. A priority score, ranking, or queue number of the scan priority data 427 can be generated by automatically by a subsystem based on the scan priority data 427, based on a severity of patient symptoms or other indicators in the risk factor data 432, based on a priority corresponding to the originating entity, based on previously generated diagnosis data 440 for the scan, and/or can be assigned by the originating entity and/or a user of the system.

The scan classifier data 420 can include other classifying data not pictured in FIG. 4A. For example, a set of scans can include medical scan image data 410 corresponding to different imaging planes. The scan classifier data can further include imaging plane data indicating one or more imaging planes corresponding to the image data. For example, the imaging plane data can indicate the scan corresponds to the axial plane, sagittal plane, or coronal plane. A single medical scan entry 352 can include medical scan image data 410 corresponding multiple planes, and each of these planes can be tagged appropriately in the image data. In other embodiments, medical scan image data 410 corresponding to each plane can be stored as separate medical scan entries 352, for example, with a common identifier indicating these entries belong to the same set of scans.

Alternatively or in addition, the scan classifier data 420 can include sequencing data. For example, a set of scans can include medical scan image data 410 corresponding to different sequences. The scan classifier data can further include sequencing data indicating one or more of a plurality of sequences of the image data corresponds to, for example, indicating whether an MRI scan corresponds to a T2 sequence, a T1 sequence, a T1 sequence with contrast, a diffusion sequence, a FLAIR sequence, or other MRI sequence. A single medical scan entry 352 can include medical scan image data 410 corresponding to multiple sequences, and each of these sequences can be tagged appropriately in the entry. In other embodiments, medical scan image data 410 corresponding to each sequence can be stored as separate medical scan entries 352, for example, with a common identifier indicating these entries belong to the same set of scans.

Alternatively or in addition, the scan classifier data 420 can include an image quality score. This score can be determined automatically by one or more subsystems 101, and/or can be manually assigned the medical scan. The image quality score can be based on a resolution of the image data 410, where higher resolution image data is assigned a more favorable image quality score than lower resolution image data. The image quality score can be based on whether the image data 410 corresponds to digitized image data received directly from the corresponding imaging machine, or corresponds to a hard copy of the image data that was later scanned in. In some embodiments, the image quality score can be based on a detected corruption, and/or detected external factor that determined to negatively affect the quality of the image data during the capturing of the medical scan and/or subsequent to the capturing of the medical scan. In some embodiments, the image quality score can be based on detected noise in the image data, where a medical scan with a higher level of detected noise can receive a less favorable image quality score than a medical scan with a lower level of detected noise. Medical scans with this determined corruption or external factor can receive a less favorable image quality score than medical scans with no detected corruption or external factor.

In some embodiments, the image quality score can be based on include machine data 425. In some embodiments, one or more subsystems can utilize the image quality score to flag medical scans with image quality scores that fall below an image quality threshold. The image quality threshold can be the same or different for different subsystems, medical scan modalities, and/or anatomical regions. For example, the medical scan image analysis system can automatically filter training sets based on selecting only medical scans with image quality scores that compare favorably to the image quality threshold. As another example, one or more subsystems can flag a particular imaging machine and/or hospital or other medical entity that have produced at least a threshold number and/or percentage of medical scan with image quality scores that compare unfavorably to the image quality threshold. As another example, a de-noising algorithm can be automatically utilized to clean the image data when the image quality score compares unfavorably to the image quality threshold. As another example, the medical scan image analysis system can select a particular medical image analysis function from a set of medical image analysis functions to utilize on a medical scan to generate inference data for the medical scan. Each of this set of medical image analysis function can be trained on different levels of image quality, and the selected image analysis function can be selected based on the determined image quality score falling within a range of image quality scores the image analysis function was trained on and/or is otherwise suitable for.

The patient history data 430 can include patient identifier data 431 which can include basic patient information such as name or an identifier that may be anonymized to protect the confidentiality of the patient, age, and/or gender. The patient identifier data 431 can also map to a patient entry in a separate patient database stored by the database storage system, or stored elsewhere. The patient history data can include patient risk factor data 432 which can include previous medical history, family medical history, smoking and/or drug habits, pack years corresponding to tobacco use, environmental exposures, patient symptoms, etc. The patient history data 430 can also include longitudinal data 433, which can identify one or more additional medical scans corresponding to the patient, for example, retrieved based on patient identifier data 431 or otherwise mapped to the patient identifier data 431. Some or all additional medical scans can be included in the medical scan database, and can be identified based on their corresponding identifiers medical scan identifiers 353. Some or all additional medical scans can be received from a different source and can otherwise be identified. Alternatively or in addition, the longitudinal data can simply include some or all relevant scan entry data of a medical scan entry 352 corresponding to the one or more additional medical scans. The additional medical scans can be the same type of scan or different types of scans. Some or all of the additional scans may correspond to past medical scans, and/or some or all of the additional scans may correspond to future medical scans. The longitudinal data 433 can also include data received and/or determined at a date after the scan such as final biopsy data, or some or all of the diagnosis data 440. The patient history data can also include a longitudinal quality score 434, which can be calculated automatically by a subsystem, for example, based on the number of additional medical scans, based on how many of the additional scans in the file were taken before and/or after the scan based on the scan date data 426 of the medical scan and the additional medical scans, based on a date range corresponding to the earliest scan and corresponding to the latest scan, based on the scan types data 421 these scans, and/or based on whether or not a biopsy or other final data is included. As used herein, a “high” longitudinal quality score refers to a scan having more favorable longitudinal data than that with a “low” longitudinal quality score.

Diagnosis data 440 can include data that indicates an automated diagnosis, a tentative diagnosis, and/or data that can otherwise be used to support medical diagnosis, triage, medical evaluation and/or other review by a medical professional or other user. The diagnosis data 440 of a medical scan can include a binary abnormality identifier 441 indicating whether the scan is normal or includes at least one abnormality. In some embodiments, the binary abnormality identifier 441 can be determined by comparing some or all of confidence score data 460 to a threshold, can be determined by comparing a probability value to a threshold, and/or can be determined by comparing another continuous or discrete value indicating a calculated likelihood that the scan contains one or more abnormalities to a threshold. In some embodiments, non-binary values, such as one or more continuous or discrete values indicating a likelihood that the scan contains one or more abnormalities, can be included in diagnosis data 440 in addition to, or instead of, binary abnormality identifier 441. One or abnormalities can be identified by the diagnosis data 440, and each identified abnormality can include its own set of abnormality annotation data 442. Alternatively, some or all of the diagnosis data 440 can indicate and/or describe multiple abnormalities, and thus will not be presented for each abnormality in the abnormality annotation data 442. For example, the report data 449 of the diagnosis data 440 can describe all identified abnormalities, and thus a single report can be included in the diagnosis.

FIG. 4B presents an embodiment of the abnormality annotation data 442. The abnormality annotation data 442 for each abnormality can include abnormality location data 443, which can include an anatomical location and/or a location specific to pixels, image slices, coordinates or other location information identifying regions of the medical scan itself. The abnormality annotation data 442 can include abnormality classification data 445 which can include binary, quantitative, and/or descriptive data of the abnormality as a whole, or can correspond to one or more abnormality classifier categories 444, which can include size, volume, pre-post contrast, doubling time, calcification, components, smoothness, spiculation, lobulation, sphericity, internal structure, texture, or other categories that can classify and/or otherwise characterize an abnormality. Abnormality classifier categories 444 can be assigned a binary value, indicating whether or not such a category is present. For example, this binary value can be determined by comparing some or all of confidence score data 460 to a threshold, can be determined by comparing a probability value to a threshold, and/or can be determined by comparing another continuous or discrete value indicating a calculated likelihood that a corresponding abnormality classifier category 444 is present to a threshold, which can be the same or different threshold for each abnormality classifier category 444. In some embodiments, abnormality classifier categories 444 can be assigned one or more non-binary values, such as one or more continuous or discrete values indicating a likelihood that the corresponding classifier category 444 is present.

The abnormality classifier categories 444 can also include a malignancy category, and the abnormality classification data 445 can include a malignancy rating such as a Lung-RADS score, a Fleischner score, and/or one or more calculated values that indicate malignancy level, malignancy severity, and/or probability of malignancy. Alternatively or in addition, the malignancy category can be assigned a value of “yes”, “no”, or “maybe”. The abnormality classifier categories 444 can also include abnormality pattern categories 446 such as cardiomegaly, consolidation, effusion, emphysema, and/or fracture, and the abnormality classification data 445 for each abnormality pattern category 446 can indicate whether or not each of the abnormality patterns is present.

The abnormality classifier categories can correspond to Response Evaluation Criteria in Solid Tumors (RECIST) eligibility and/or RECIST evaluation categories. For example, an abnormality classifier category 444 corresponding to RECIST eligibility can have corresponding abnormality classification data 445 indicating a binary value “yes” or “no”, and/or can indicate if the abnormality is a “target lesion” and/or a “non-target lesion.” As another example, an abnormality classifier category 444 corresponding to a RECIST evaluation category can be determined based on longitudinal data 433 and can have corresponding abnormality classification data 445 that includes one of the set of possible values “Complete Response”, “Partial Response”, “Stable Disease”, or “Progressive Disease.”

The diagnosis data 440 as a whole, and/or the abnormality annotation data 442 for each abnormality, can include custom codes or datatypes identifying the binary abnormality identifier 441, abnormality location data 443 and/or some or all of the abnormality classification data 445 of one or more abnormality classifier categories 444. Alternatively or in addition, some or all of the abnormality annotation data 442 for each abnormality and/or other diagnosis data 440 can be presented in a DICOM format or other standardized image annotation format, and/or can be extracted into custom datatypes based on abnormality annotation data originally presented in DICOM format. Alternatively or in addition, the diagnosis data 440 and/or the abnormality annotation data 442 for each abnormality can be presented as one or more medical codes 447 such as SNOMED codes, Current Procedure Technology (CPT) codes, ICD-9 codes, ICD-10 codes, or other standardized medical codes used to label or otherwise describe medical scans.

Alternatively or in addition, the diagnosis data 440 can include natural language text data 448 annotating or otherwise describing the medical scan as a whole, and/or the abnormality annotation data 442 can include natural language text data 448 annotating or otherwise describing each corresponding abnormality. In some embodiments, some or all of the diagnosis data 440 is presented only as natural language text data 448. In some embodiments, some or all of the diagnosis data 440 is automatically generated by one or more subsystems based on the natural language text data 448, for example, without utilizing the medical scan image data 410, for example, by utilizing one or more medical scan natural language analysis functions trained by the medical scan natural language analysis system 114. Alternatively or in addition, some embodiments, some or all of the natural language text data 448 is generated automatically based on other diagnosis data 440 such as abnormality annotation data 442, for example, by utilizing a medical scan natural language generating function trained by the medical scan natural language analysis system 114.

The diagnosis data can include report data 449 that includes at least one medical report, which can be formatted to include some or all of the medical codes 447, some or all of the natural language text data 448, other diagnosis data 440, full or cropped images slices formatted based on the display parameter data 470 and/or links thereto, full or cropped images slices or other data based on similar scans of the similar scan data 480 and/or links thereto, full or cropped images or other data based on patient history data 430 such as longitudinal data 433 and/or links thereto, and/or other data or links to data describing the medical scan and associated abnormalities. The diagnosis data 440 can also include finalized diagnosis data corresponding to future scans and/or future diagnosis for the patient, for example, biopsy data or other longitudinal data 433 determined subsequently after the scan. The medical report of report data 449 can be formatted based on specified formatting parameters such as font, text size, header data, bulleting or numbering type, margins, file type, preferences for including one or more full or cropped image slices 412, preferences for including similar medical scans, preferences for including additional medical scans, or other formatting to list natural language text data and/or image data, for example, based on preferences of a user indicated in the originating entity data 423 or other responsible user in the corresponding report formatting data.

Annotation author data 450 can be mapped to the diagnosis data for each abnormality, and/or mapped to the scan as a whole. This can include one or more annotation author identifiers 451, which can include one or more user profile identifiers of a user of the system, such as an individual medical professional, medical facility and/or medical entity that uses the system. Annotation author data 450 can be used to determine the usage data of a user profile entry 354. Annotation author data 450 can also include one or more medical scan analysis function identifiers 357 or other function identifier indicating one or more functions or other processes of a subsystem responsible for automatically generating and/or assisting a user in generating some or all of the diagnosis data, for example an identifier of a particular type and/or version of a medical scan image analysis functions that was used by the medical scan diagnosing system 108 used to generate part or all of the diagnosis data 440 and/or an interface feature identifier, indicating an one or more interface features presented to a user to facilitate entry of and/or reviewing of the diagnosis data 440. The annotation author data can also simply indicate, for one or more portions of the diagnosis data 440, if this portion was generated by a human or automatically generated by a subsystem of the medical scan processing system.

In some embodiments, if a medical scan was reviewed by multiple entities, multiple, separate diagnosis data entries 440 can be included in the medical scan entry 352, mapped to each diagnosis author in the annotation author data 450. This allows different versions of diagnosis data 440 received from multiple entities. For example, annotation author data of a particular medical scan could indicate that the annotation data was written by a doctor at medical entity A, and the medical code data was generated by user Y by utilizing the medical scan report labeling system 104, which was confirmed by expert user X. The annotation author data of another medical scan could indicate that the medical code was generated automatically by utilizing version 7 of the medical scan image analysis function relating to chest x-rays, and confirmed by expert user X. The annotation author data of another medical scan could indicate that the location and a first malignancy rating were generated automatically by utilizing version 7 of the medical scan image analysis function relating to chest x-rays, and that a second malignancy rating was entered by user Z. In some embodiments, one of the multiple diagnosis entries can include consensus annotation data, for example, generated automatically by a subsystem such as the medical scan annotating system 106 based on the multiple diagnosis data 440, based on confidence score data 460 of each of the multiple diagnosis data 440, and/or based on performance score data of a corresponding user, a medical scan analysis function, or an interface feature, identified in the annotation author data for each corresponding one of the multiple diagnosis data 440.

Confidence score data 460 can be mapped to some or all of the diagnosis data 440 for each abnormality, and/or for the scan as a whole. This can include an overall confidence score for the diagnosis, a confidence score for the binary indicator of whether or not the scan was normal, a confidence score for the location a detected abnormality, and/or confidence scores for some or all of the abnormality classifier data. This may be generated automatically by a subsystem, for example, based on the annotation author data and corresponding performance score of one or more identified users and/or subsystem attributes such as interactive interface types or medical scan image analysis functions indicated by the annotation author data. In the case where multiple diagnosis data entries 440 are included from different sources, confidence score data 460 can be computed for each entry and/or an overall confidence score, for example, corresponding to consensus diagnosis data, can be based on calculated distance or other error and/or discrepancies between the entries, and/or can be weighted on the confidence score data 460 of each entry. In various embodiments, the confidence score data 460 can include a truth flag 461 indicating the diagnosis data is considered as “known” or “truth”, for example, flagged based on user input, flagged automatically based on the author data, and/or flagged automatically based on the calculated confidence score of the confidence score data exceeding a truth threshold. As used herein, a “high” confidence score refers to a greater degree or more favorable level of confidence than a “low” confidence score.

Display parameter data 470 can indicate parameters indicating an optimal or preferred display of the medical scan by an interactive interface 275 and/or formatted report for each abnormality and/or for the scan as a whole. Some or all of the display parameter data can have separate entries for each abnormality, for example, generated automatically by a subsystem 101 based on the abnormality annotation data 442. Display parameter data 470 can include interactive interface feature data 471, which can indicate one or more selected interface features associated with the display of abnormalities and/or display of the medical scan as a whole, and/or selected interface features associated with user interaction with a medical scan, for example, based on categorized interface feature performance score data and a category associated with the abnormality and/or with the medical scan itself. The display parameter data can include a slice subset 472, which can indicate a selected subset of the plurality of image slices that includes a single image slice 412 or multiple image slices 412 of the medical scan image data 410 for display by a user interface. The display parameter data 470 can include slice order data 473 that indicates a selected custom ordering and/or ranking for the slice subset 472, or for all of the slices 412 of the medical scan. The display parameter data 470 can include slice cropping data 474 corresponding to some or all of the slice subset 472, or all of the image slices 412 of the medical scan, and can indicating a selected custom cropped region of each image slice 412 for display, or the same selected custom cropped region for the slice subset 472 or for all slices 412. The display parameter data can include density window data 475, which can indicate a selected custom density window for display of the medical scan as a whole, a selected custom density window for the slice subset 472, and/or selected custom density windows for each of the image slices 412 of the slice subset 472, and/or for each image slice 412 of the medical scan. The density window data 475 can indicate a selected upper density value cut off and a selected lower density value cut off, and/or can include a selected deterministic function to map each density value of a pixel to a grayscale value based on the preferred density window. The interactive interface feature data 471, slice subset 472, slice order data 473, slice cropping data 474, and/or the density window data 475 can be selected via user input and/or generated automatically by one or more subsystems 101, for example, based on the abnormality annotation data 442 and/or based on performance score data of different interactive interface versions.

Similar scan data 480 can be mapped to each abnormality, or the scan as a whole, and can include similar scan identifier data 481 corresponding to one or more identified similar medical scans, for example, automatically identified by a subsystem 101, for example, by applying a similar scan identification step of the medical scan image analysis system 112 and/or applying medical scan similarity analysis function to some or all of the data stored in the medical scan entry of the medical scan, and/or to some or all corresponding data of other medical scans in the medical scan database. The similar scan data 480 can also correspond to medical scans received from another source. The stored similarity data can be used to present similar cases to users of the system and/or can be used to train medical scan image analysis functions or medical scan similarity analysis functions.

Each identified similar medical scan can have its own medical scan entry 352 in the medical scan database 342 with its own data, and the similar scan identifier data 481 can include the medical scan identifier 353 each similar medical scan. Each identified similar medical scan can be a scan of the same scan type or different scan type than medical scan.

The similar scan data 480 can include a similarity score 482 for each identified similar scan, for example, generated based on some or all of the data of the medical scan entry 352 for medical scan and based on some or all of the corresponding data of the medical scan entry 352 for the identified similar medical scan. For example, the similarity score 482 can be generated based on applying a medical scan similarity analysis function to the medical image scan data of medical scans and 402, to some or all of the abnormality annotation data of medical scans and 402, and/or to some or all of the patient history data 430 of medical scans and 402 such as risk factor data 432. As used herein, a “high” similarity score refers a higher level of similarity that a “low” similarity score.

The similar scan data 480 can include its own similar scan display parameter data 483, which can be determined based on some or all of the display parameter data 470 of the identified similar medical scan. Some or all of the similar scan display parameter data 483 can be generated automatically by a subsystem, for example, based on the display parameter data 470 of the identified similar medical scan, based on the abnormality annotation data 442 of the medical scan itself and/or based on display parameter data 470 of the medical scan itself. Thus, the similar scan display parameter data 483 can be the same or different than the display parameter data 470 mapped to the identified similar medical scan and/or can be the same or different than the display parameter data 470 of the medical scan itself. This can be utilized when displaying similar scans to a user via interactive interface 275 and/or can be utilized when generating report data 449 that includes similar scans, for example, in conjunction with the medical scan assisted review system 102.

The similar scan data 480 can include similar scan abnormality data 484, which can indicate one of a plurality of abnormalities of the identified similar medical scan and its corresponding abnormality annotation data 442. For example, the similarity scan abnormality data 484 can include an abnormality pair that indicates one of a plurality of abnormalities of the medical scan, and indicates one of a plurality of abnormalities of the identified similar medical scan, for example, that was identified as the similar abnormality.

The similar scan data 480 can include similar scan filter data 485. The similar scan filter data can be generated automatically by a subsystem, and can include a selected ordered or un-ordered subset of all identified similar scans of the similar scan data 480, and/or a ranking of all identified similar scans. For example, the subset can be selected and/or some or all identified similar scans can be ranked based on each similarity score 482, and/or based on other factors such as based on a longitudinal quality score 434 of each identified similar medical scan.

The training set data 490 can indicate one or more training sets that the medical scan belongs to. For example, the training set data can indicate one or more training set identifiers 491 indicating one or more medical scan analysis functions that utilized the medical scan in their training set, and/or indicating a particular version identifier 641 of the one or more medical scan analysis functions that utilized the medical scan in their training set. The training set data 490 can also indicate which portions of the medical scan entry were utilized by the training set, for example, based on model parameter data 623 of the corresponding medical scan analysis functions. For example, the training set data 490 can indicate that the medical scan image data 410 was included in the training set utilized to train version X of the chest x-ray medical scan image analysis function, or that the natural language text data 448 of this medical scan was used to train version Y of the natural language analysis function.

FIG. 5A presents an embodiment of a user profile entry 354, stored in user database 344 or otherwise associated with a user. A user can correspond to a user of one or more of the subsystems such as a radiologist, doctor, medical professional, medical report labeler, administrator of one or more subsystems or databases, or other user that uses one or more subsystems 101. A user can also correspond to a medical entity such as a hospital, medical clinic, establishment that utilizes medical scans, establishment that employs one or more of the medical professionals described, an establishment associated with administering one or more subsystems, or other entity. A user can also correspond to a particular client device 120 or account that can be accessed one or more medical professionals or other employees at the same or different medical entities. Each user profile entry can have a corresponding user profile identifier 355.

A user profile entry 354 can include basic user data 510, which can include identifying information 511 corresponding to the user such as a name, contact information, account/login/password information, geographic location information such as geographic region data 424, and/or other basic information. Basic user data 510 can include affiliation data 512, which can list one or more medical entities or other establishments the user is affiliated with, for example, if the user corresponds to a single person such as a medical professional, or if the user corresponds to a hospital in a network of hospitals. The affiliation data 512 can include one or more corresponding user profile identifiers 355 and/or basic user data 510 if the corresponding affiliated medical entity or other establishment has its own entry in the user database. The user identifier data can include employee data 513 listing one or more employees, such as medical professionals with their own user profile entries 354, for example, if the user corresponds to a medical entity or supervising medical professional of other medical professional employees, and can list a user profile identifier 355 and/or basic user data 510 for each employee. The basic user data 510 can also include imaging machine data 514, which can include a list of machines affiliated with the user which can include machine identifiers, model information, calibration information, scan type information, or other data corresponding to each machine, for example, corresponding to the machine data 425. The user profile entry can include client device data 515, which can include identifiers for one or more client devices associated with the user, for example, allowing subsystems 101 to send data to a client device 120 corresponding to a selected user based on the client device data and/or to determine a user that data was received by determining the client device from which the data was received.

The user profile entry can include usage data 520 which can include identifying information for a plurality of usages by the user in conjunction with using one or more subsystems 101. This can include consumption usage data 521, which can include a listing of, or aggregate data associated with, usages of one or more subsystems by the user, for example, where the user is utilizing the subsystem as a service. For example, the consumption usage data 521 can correspond to each instance where diagnosis data was sent to the user for medical scans provided to the user in conjunction with the medical scan diagnosing system 108 and/or the medical scan assisted review system 102. Some or all of consumption usage data 521 can include training usage data 522, corresponding to usage in conjunction with a certification program or other user training provided by one or more subsystems. The training usage data 522 can correspond to each instance where diagnosis feedback data was provided by user for a medical scan with known diagnosis data, but diagnosis feedback data is not utilized by a subsystem to generate, edit, and/or confirm diagnosis data 440 of the medical scan, as it is instead utilized to train a user and/or determine performance data for a user.

Usage data 520 can include contribution usage data 523, which can include a listing of, or aggregate data associated with, usages of one or more subsystems 101 by the user, for example, where the user is generating and/or otherwise providing data and/or feedback that can is utilized by the subsystems, for example, to generate, edit, and/or confirm diagnosis data 440 and/or to otherwise populate, modify, or confirm portions of the medical scan database or other subsystem data. For example, the contribution usage data 523 can correspond to diagnosis feedback data received from user, used to generate, edit, and/or confirm diagnosis data. The contribution usage data 523 can include interactive interface feature data 524 corresponding to the interactive interface features utilized with respect to the contribution.

The consumption usage data 521 and/or the contribution usage data 523 can include medical scan entry 352 whose entries the user utilized and/or contributed to, can indicate one or more specific attributes of a medical scan entry 352 that a user utilized and/or contributed to, and/or a log of the user input generated by a client device of the user in conjunction with the data usage. The contribution usage data 523 can include the diagnosis data that the user may have generated and/or reviewed, for example, indicated by, mapped to, and/or used to generate the annotation author data 450 of corresponding medical scan entries 352. Some usages may correspond to both consumption usage of the consumption usage data 521 and contribution usage of the contribution usage data 523. The usage data 520 can also indicate one or more subsystems 101 that correspond to each consumption and/or contribution.

The user profile entry can include performance score data 530. This can include one or more performance scores generated based on the contribution usage data 523 and/or training usage data 522. The performance scores can include separate performance scores generated for every contribution in the contribution usage data 523 and/or training usage data 522 and/or generated for every training consumption usages corresponding to a training program. As used herein, a “high” performance score refers to a more favorable performance or rating than a “low” performance score.

The performance score data can include accuracy score data 531, which can be generated automatically by a subsystem for each contribution, for example, based on comparing diagnosis data received from a user to data to known truth data such as medical scans with a truth flag 461, for example, retrieved from the corresponding medical scan entry 352 and/or based on other data corresponding to the medical scan, for example, received from an expert user that later reviewed the contribution usage data of the user and/or generated automatically by a subsystem. The accuracy score data 531 can include an aggregate accuracy score generated automatically by a subsystem, for example, based on the accuracy data of multiple contributions by the user over time.

The performance data can also include efficiency score data 532 generated automatically by a subsystem for each contribution based on an amount of time taken to complete a contribution, for example, from a time the request for a contribution was sent to the client device to a time that the contribution was received from the client device, based on timing data received from the client device itself, and/or based on other factors. The efficiency score can include an aggregate efficiency score, which can be generated automatically by a subsystem based on the individual efficiency scores over time and/or based on determining a contribution completion rate, for example based on determining how many contributions were completed in a fixed time window.

Aggregate performance score data 533 can be generated automatically by a subsystem based on the aggregate efficiency and/or accuracy data. The aggregate performance data can include categorized performance data 534, for example, corresponding to different scan types, different anatomical regions, different subsystems, different interactive interface features and/or display parameters. The categorized performance data 534 can be determined automatically by a subsystem based on the scan type data 421 and/or anatomical region data 422 of the medical scan associated with each contribution, one or more subsystems 101 associated with each contribution, and/or interactive interface feature data 524 associated with each contribution. The aggregate performance data can also be based on performance score data 530 of individual employees if the user corresponds to a medical entity, for example, retrieved based on user profile identifiers 355 included in the employee data 513. The performance score data can also include ranking data 535, which can include an overall ranking or categorized rankings, for example, generated automatically by a subsystem or the database itself based on the aggregate performance data.

In some embodiments, aggregate data for each user can be further broken down based on scores for distinct scan categories, for example, based on the scan classifier data 420, for example, where a first aggregate data score is generated for a user “A” based on scores from all knee x-rays, and a second aggregate data score is generated for user A based on scores from all chest CT scans. Aggregate data for each user can be further based on scores for distinct diagnosis categories, where a first aggregate data score is generated for user A based on scores from all normal scans, and a second aggregate data score is generated for user A based on scores from all scans that contain an abnormality. This can be further broken down, where a first aggregate score is generated for user A based on all scores from scans that contain an abnormality of a first type and/or in a first anatomical location, and a second aggregate score is generated for A based on all scores from scans that contain an abnormality of a second type and/or in a second location. Aggregate data for each user can be further based on affiliation data, where a ranking is generated for a medical professional “B” based on scores from all medical professionals with the same affiliation data, and/or where a ranking is generated for a hospital “C” based on scores for all hospitals, all hospitals in the same geographical region, etc. Aggregate data for each user can be further based on scores for interface features, where a first aggregate data score is generated for user A based on scores using a first interface feature, and a second aggregate data score is generated for user A based on scores using a first interface feature.

The user profile entry can include qualification data 540. The qualification data can include experience data 541 such as education data, professional practice data, number of years practicing, awards received, etc. The qualification data 540 can also include certification data 542 corresponding to certifications earned based on contributions to one or more subsystems, for example, assigned to users automatically by a subsystem based on the performance score data 530 and/or based on a number of contributions in the contribution usage data 523 and/or training usage data 522. For example, the certifications can correspond to standard and/or recognized certifications to train medical professionals and/or incentivize medical professionals to use the system. The qualification data 540 can include expert data 543. The expert data 543 can include a binary expert identifier, which can be generated automatically by a subsystem based on experience data 541, certification data 542, and/or the performance score data 530, and can indicate whether the user is an expert user. The expert data 543 can include a plurality of categorized binary expert identifiers corresponding to a plurality of qualification categories corresponding to corresponding to scan types, anatomical regions, and/or the particular subsystems. The categorized binary expert identifiers can be generated automatically by a subsystem based on the categorized performance data 534 and/or the experience data 541. The categories be ranked by performance score in each category to indicate particular specialties. The expert data 543 can also include an expert ranking or categorized expert ranking with respect to all experts in the system.

The user profile entry can include subscription data 550, which can include a selected one of a plurality of subscription options that the user has subscribed to. For example, the subscription options can correspond to allowed usage of one or more subsystems, such as a number of times a user can utilize a subsystem in a month, and/or to a certification program, for example paid for by a user to receive training to earn a subsystem certification of certification data 542. The subscription data can include subscription expiration information, and/or billing information. The subscription data can also include subscription status data 551, which can for example indicate a number of remaining usages of a system and/or available credit information. For example, the remaining number of usages can decrease and/or available credit can decrease in response to usages that utilize one or more subsystems as a service, for example, indicated in the consumption usage data 521 and/or training usage data 522. In some embodiments, the remaining number of usages can increase and/or available credit can increase in response to usages that correspond to contributions, for example, based on the contribution usage data 523. An increase in credit can be variable, and can be based on a determined quality of each contribution, for example, based on the performance score data 530 corresponding to the contribution where a higher performance score corresponds to a higher increase in credit, based on scan priority data 427 of the medical scan where contributing to higher priority scans corresponds to a higher increase in credit, or based on other factors.

The user profile entry 354 can include interface preference data 560. The interface preference data can include a preferred interactive interface feature set 561, which can include one or more interactive interface feature identifiers and/or one or more interactive interface version identifiers of interface feature entries 358 and/or version identifiers of the interface features. Some or all of the interface features of the preferred interactive interface feature set 561 can correspond to display parameter data 470 of medical scans. The preferred interactive interface feature set 561 can include a single interactive feature identifier for one or more feature types and/or interface types, and/or can include a single interactive interface version identifier for one or more interface categories. The preferred interactive interface feature set 561 can include a ranking of multiple features for the same feature type and/or interface type. The ranked and/or unranked preferred interactive interface feature set 561 can be generated based on user input to an interactive interface of the client device to select and/or rank some or all of the interface features and/or versions. Some or all of the features and/or versions of the preferred interactive feature set can be selected and/or ranked automatically by a subsystem such as the medical scan interface evaluator system, for example based on interface feature performance score data and/or feature popularity data. Alternatively or in addition, the performance score data 530 can be utilized by a subsystem to automatically determine the preferred interactive feature set, for example, based on the scores in different feature-based categories of the categorized performance data 534.

The user profile entry 354 can include report formatting data 570, which can indicate report formatting preferences indicated by the user. This can include font, text size, header data, bulleting or numbering type, margins, file type, preferences for including one or more full or cropped image slices 412, preferences for including similar medical scans, preferences for including additional medical scans in reports, or other formatting preference to list natural language text data and/or image data corresponding to each abnormality. Some or all of the report formatting data 570 can be based on interface preference data 560. The report formatting data 570 can be used by one or more subsystems to automatically generate report data 449 of medical scans based on the preferences of the requesting user.

FIG. 5B presents an embodiment of a medical scan analysis function entry 356, stored in medical scan analysis function database 346 or otherwise associated with one of a plurality of medical scan analysis functions trained by and/or utilized by one or more subsystems 101. For example, a medical scan analysis function can include one or more medical scan image analysis functions trained by the medical scan image analysis system 112; one or more medical scan natural language analysis functions trained by the medical scan natural language analysis system 114; one or more medical scan similarity analysis function trained by the medical scan image analysis system 112, the medical scan natural language analysis system 114, and/or the medical scan comparison system 116; one or more medical report generator functions trained by the medical scan natural language analysis system 114 and/or the medical scan image analysis system 112, and/or the medical report analysis function trained by the medical scan natural language analysis system 114. Some or all of the medical scan analysis functions can correspond to medical scan inference functions of the medical scan diagnosing system 108, the de-identification function and/or the inference functions utilized by a medical picture archive integration system as discussed in conjunction with FIGS. 8A-8F, or other functions and/or processes described herein in conjunction with one or more subsystems 101. Each medical scan analysis function entry 356 can include a medical scan analysis function identifier 357.

A medical scan analysis function entry 356 can include function classifier data 610. Function classifier data 610 can include input and output types corresponding to the function. For example the function classifier data can include input scan category 611 that indicates which types of scans can be used as input to the medical scan analysis function. For example, input scan category 611 can indicate that a medical scan analysis function is for chest CT scans from a particular hospital or other medical entity. The input scan category 611 can include one or more categories included in scan classifier data 420. In various embodiments, the input scan category 611 corresponds to the types of medical scans that were used to train the medical scan analysis function. Function classifier data 610 can also include output type data 612 that characterizes the type of output that will be produced by the function, for example, indicating that a medical scan analysis function is used to generate medical codes 447. The input scan category 611 can also include information identifying which subsystems 101 are responsible for running the medical scan analysis function.

A medical scan analysis function entry 356 can include training parameters 620. This can include training set data 621, which can include identifiers for the data used to train the medical scan analysis function, such as a set of medical scan identifiers 353 corresponding to the medical scans used to train the medical scan analysis function, a list of medical scan reports and corresponding medical codes used to train the medical scan analysis function, etc. Alternatively or in addition to identifying particular scans of the training set, the training set data 621 can identify training set criteria, such as necessary scan classifier data 420, necessary abnormality locations, classifiers, or other criteria corresponding to abnormality annotation data 442, necessary confidence score data 460, for example, indicating that only medical scans with diagnosis data 440 assigned a truth flag 461 or with confidence score data 460 otherwise comparing favorably to a training set confidence score threshold are included, a number of medical scans to be included and proportion data corresponding to different criteria, or other criteria used to populate a training set with data of medical scans. Training parameters 620 can include model type data 622 indicating one or more types of model, methods, and/or training functions used to determine the medical scan analysis function by utilizing the training set 621. Training parameters 620 can include model parameter data 623 that can include a set of features of the training data selected to train the medical scan analysis function, determined values for weights corresponding to selected input and output features, determined values for model parameters corresponding to the model itself, etc. The training parameter data can also include testing data 624, which can identify a test set of medical scans or other data used to test the medical scan analysis function. The test set can be a subset of training set 621, include completely separate data than training set 621, and/or overlap with training set 621. Alternatively or in addition, testing data 624 can include validation parameters such as a percentage of data that will be randomly or pseudo-randomly selected from the training set for testing, parameters characterizing a cross validation process, or other information regarding testing. Training parameters 620 can also include training error data 625 that indicates a training error associated with the medical scan analysis function, for example, based on applying cross validation indicated in testing data 624.

A medical scan analysis function entry 356 can include performance score data 630. Performance data can include model accuracy data 631, for example, generated and/or updated based on the accuracy of the function when performed on new data. For example, the model accuracy data 631 can include or be calculated based on the model error for determined for individual uses, for example, generated by comparing the output of the medical scan analysis function to corresponding data generated by user input to interactive interface 275 in conjunction with a subsystem 101 and/or generated by comparing the output of the medical scan analysis function to medical scans with a truth flag 461. The model accuracy data 631 can include aggregate model accuracy data computed based on model error of individual uses of the function over time. The performance score data 630 can also include model efficiency data 632, which can be generated based on how quickly the medical scan analysis function performs, how much memory is utilized by medical scan analysis function, or other efficiency data relating to the medical scan analysis function. Some or all of the performance score data 630 can be based on training error data 625 or other accuracy and/or efficiency data determined during training and/or validation. As used herein, a “high” performance score refers to a more favorable performance or rating than a “low” performance score.

A medical scan analysis function entry 356 can include version data 640. The version data can include a version identifier 641. The version data can indicate one or more previous version identifiers 642, which can map to version identifiers 641 stored in other medical scan analysis function entry 356 that correspond to previous versions of the function. Alternatively or in addition, the version data can indicate multiple versions of the same type based on function classifier data 610, can indicate the corresponding order and/or rank of the versions, and/or can indicate training parameters 620 associated with each version.

A medical scan analysis function entry 356 can include remediation data 650. Remediation data 650 can include remediation instruction data 651 which can indicate the steps in a remediation process indicating how a medical scan analysis function is taken out of commission and/or reverted to a previous version in the case that remediation is necessary. The version data 640 can further include remediation criteria data 652, which can include threshold data or other criteria used to automatically determine when remediation is necessary. For example, the remediation criteria data 652 can indicate that remediation is necessary at any time where the model accuracy data and/or the model efficiency data compares unfavorably to an indicated model accuracy threshold and/or indicated model efficiency threshold. The remediation data 650 can also include recommissioning instruction data 653, identifying required criteria for recommissioning a medical scan analysis function and/or updating a medical scan analysis function. The remediation data 650 can also include remediation history, indicating one or more instances that the medical scan analysis function was taken out of commission and/or was recommissioned.

FIGS. 6A and 6B present an embodiment of a medical scan diagnosing system 108.

The medical scan diagnosing system 108 can generate inference data 1110 for medical scans by utilizing a set of medical scan inference functions 1105, stored and run locally, stored and run by another subsystem 101, and/or stored in the medical scan analysis function database 346, where the function and/or parameters of the function can be retrieved from the database by the medical scan diagnosing system. For example, the set of medical scan inference function 1105 can include some or all medical scan analysis functions described herein or other functions that generate inference data 1110 based on some or all data corresponding to a medical scan such as some or all data of a medical scan entry 352. Each medical scan inference function 1105 in the set can correspond to a scan category 1120, and can be trained on a set of medical scans that compare favorably to the scan category 1120. For example, each inference function can be trained on a set of medical scans of the one or more same scan classifier data 420, such as the same and/or similar scan types, same and/or similar anatomical regions locations, same and/or similar machine models, same and/or similar machine calibration, same and/or similar contrasting agent used, same and/or similar originating entity, same and/or similar geographical region, and/or other classifiers. Thus, the scan categories 1120 can correspond to one or more of a scan type, scan anatomical region data, hospital or other originating entity data, machine model data, machine calibration data, contrast agent data, geographic region data, and/or other scan classifying data 420. For example, a first medical scan inference function can be directed to characterizing knee x-rays, and a second medical scan inference function can be directed to chest CT scans. As another example, a first medical scan inference function can be directed to characterizing CT scans from a first hospital, and a second medical scan image analysis function can be directed to characterizing CT scans from a second hospital.

Training on these categorized sets separately can ensure each medical scan inference function 1105 is calibrated according to its scan category 1120, for example, allowing different inference functions to be calibrated on type specific, anatomical region specific, hospital specific, machine model specific, and/or region-specific tendencies and/or discrepancies. Some or all of the medical scan inference functions 1105 can be trained by the medical scan image analysis system and/or the medical scan natural language processing system, and/or some medical scan inference functions 1105 can utilize both image analysis and natural language analysis techniques to generate inference data 1110. For example, some or all of the inference functions can utilize image analysis of the medical scan image data 410 and/or natural language data extracted from abnormality annotation data 442 and/or report data 449 as input, and generate diagnosis data 440 such as medical codes 447 as output. Each medical scan inference function can utilize the same or different learning models to train on the same or different features of the medical scan data, with the same or different model parameters, for example indicated in the model type data 622 and model parameter data 623. Model type and/or parameters can be selected for a particular medical scan inference function based on particular characteristics of the one or more corresponding scan categories 1120, and some or all of the indicated in the model type data 622 and model parameter data 623 can be selected automatically by a subsystem during the training process based on the particular learned and/or otherwise determined characteristics of the one or more corresponding scan categories 1120.

As shown in FIG. 6A, the medical scan diagnosing system 108 can automatically select a medical scan for processing in response to receiving it from a medical entity via the network. Alternatively, the medical scan diagnosing system 108 can automatically retrieve a medical scan from the medical scan database that is selected based on a request received from a user for a particular scan and/or based on a queue of scans automatically ordered by the medical scan diagnosing system 108 or another subsystem based on scan priority data 427.

Once a medical scan to be processed is determined, the medical scan diagnosing system 108 can automatically select an inference function 1105 based on a determined scan category 1120 of the selected medical scan and based on corresponding inference function scan categories. The scan category 1120 of a scan can be determined based one some or all of the scan classifier data 420 and/or based on other metadata associated with the scan. This can include determining which one of the plurality of medical scan inference functions 1105 matches or otherwise compares favorably to the scan category 1120, for example, by comparing the scan category 1120 to the input scan category of the function classifier data 610.

Alternatively or in addition, the medical scan diagnosing system 108 can automatically determine which medical scan inference function 1105 is utilized based on an output preference that corresponding to a desired type of inference data 1110 that is outputted by an inference function 1105. The output preference designated by a user of the medical scan diagnosing system 108 and/or based on the function of a subsystem 101 utilizing the medical scan diagnosing system 108. For example, the set of inference functions 1105 can include inference functions that are utilized to indicate whether or not a medical scan is normal, to automatically identify at least one abnormality in the scan, to automatically characterize the at least one abnormality in the scan, to assign one or more medical codes to the scan, to generate natural language text data and/or a formatted report for the scan, and/or to automatically generate other diagnosis data such as some or all of diagnosis data 440 based on the medical scan. Alternatively or in addition, some inference functions can also be utilized to automatically generate confidence score data 460, display parameter data 470, and/or similar scan data 480. The medical scan diagnosing system 108 can compare the output preference to the output type data 612 of the medical scan inference function 1105 to determine the selected inference function 1105. For example, this can be used to decide between a first medical scan inference function that automatically generates medical codes and a second medical scan inference function that automatically generates natural language text for medical reports based on the desired type of inference data 1110.

Prior to performing the selected medical scan inference function 1105, the medical scan diagnosing system 108 can automatically perform an input quality assurance function 1106 to ensure the scan classifier data 420 or other metadata of the medical scan accurately classifies the medical scan such that the appropriate medical scan inference function 1105 of the appropriate scan category 1120 is selected. The input quality assurance function can be trained on, for example, medical scan image data 410 of plurality of previous medical scans with verified scan categories. Thus, the input quality assurance function 1106 can take medical scan image data 410 as input and can generate an inferred scan category as output. The inferred scan category can be compared to the scan category 1120 of the scan, and the input quality assurance function 1106 can determine whether or not the scan category 1120 is appropriate by determining whether the scan category 1120 compares favorably to the automatically generated inferred scan category. The input quality assurance function 1106 can also be utilized to reassign the generated inferred scan category to the scan category 1120 when the scan category 1120 compares favorably to the automatically generated inferred scan category. The input quality assurance function 1106 can also be utilized to assign the generated inferred scan category to the scan category 1120 for incoming medical scans that do not include any classifying data, and/or to add classifiers in scan classifier data 420 to medical scans missing one or more classifiers.

In various embodiments, upon utilizing the input quality assurance function 1106 to determine that the scan category 1120 determined by a scan classifier data 420 or other metadata is inaccurate, the medical scan diagnosing system 108 can transmit an alert and/or an automatically generated inferred scan category to the medical entity indicating that the scan is incorrectly classified in the scan classifier data 420 or other metadata. In some embodiments, the medical scan diagnosing system 108 can automatically update performance score data corresponding to the originating entity of the scan indicated in originating entity data 423, or another user or entity responsible for classifying the scan, for example, where a lower performance score is generated in response to determining that the scan was incorrectly classified and/or where a higher performance score is generated in response to determining that the scan was correctly classified.

In some embodiments, the medical scan diagnosing system 108 can transmit the medical scan and/or the automatically generated inferred scan category to a selected user. The user can be presented the medical scan image data 410 and/or other data of the medical scan via the interactive interface 275, for example, displayed in conjunction with the medical scan assisted review system 102. The interface can prompt the user to indicate the appropriate scan category 1120 and/or prompt the user to confirm and/or edit the inferred scan category, also presented to the user. For example, scan review data can be automatically generated to reflect the user generated and/or verified scan category 1120, This user indicated scan category 1120 can be utilized to select to the medical scan inference function 1105 and/or to update the scan classifier data 420 or other metadata accordingly. In some embodiments, for example, where the scan review data indicates that the selected user disagrees with the automatically generated inferred scan category created by the input quality assurance function 1106, the medical scan diagnosing system 108 can automatically update performance score data 630 of the input quality assurance function 1106 by generating a low performance score and/or determine to enter the remediation step 1140 for the input quality assurance function 1106.

The medical scan diagnosing system 108 can also automatically perform an output quality assurance step after a medical scan inference function 1105 has been performed on a medical scan to produce the inference data 1110, as illustrated in the embodiment presented in FIG. 6B. The output quality assurance step can be utilized to ensure that the selected medical scan inference function 1105 generated appropriate inference data 1110 based on expert feedback. The inference data 1110 generated by performing the selected medical scan inference function 1105 can be sent to a client device 120 of a selected expert user, such as an expert user in the user database selected based on categorized performance data and/or qualification data that corresponds to the scan category 1120 and/or the inference itself, for example, by selecting an expert user best suited to review an identified abnormality classifier category 444 and/or abnormality pattern category 446 in the inference data 1110 based on categorized performance data and/or qualification data of a corresponding user entry. The selected user can also correspond to a medical professional or other user employed at the originating entity and/or corresponding to the originating medical professional, indicated in the originating entity data 423.

FIG. 6B illustrates an embodiment of the medical scan diagnosing system 108 in conjunction with performing a remediation step 1140. The medical scan diagnosing system 108 can monitor the performance of the set of medical scan inference functions 1105, for example, based on evaluating inference accuracy data outputted by an inference data evaluation function and/or based monitoring on the performance score data 630 in the medical scan analysis function database, and can determine whether or not if the corresponding medical scan inference function 1105 is performing properly. This can include, for example, determining if a remediation step 1140 is necessary for a medical scan inference function 1105, for example, by comparing the performance score data 630 and/or inference accuracy data to remediation criteria data 652. Determining if a remediation step 1140 is necessary can also be based on receiving an indication from the expert user or another user that remediation is necessary for one or more identified medical scan inference functions 1105 and/or for all of the medical scan inference functions 1105.

In various embodiments, a remediation evaluation function is utilized to determine if a remediation step 1140 is necessary for medical scan inference function 1105. The remediation evaluation function can include determining that remediation is necessary when recent accuracy data and/or efficiency data of a particular medical scan inference function 1105 is below the normal performance level of the particular inference function. The remediation evaluation function can include determining that remediation is necessary when recent or overall accuracy data and/or efficiency data of a particular medical scan inference function 1105 is below a recent or overall average for all or similar medical scan inference functions 1105. The remediation evaluation function can include determining that remediation is necessary only after a threshold number of incorrect diagnoses are made. In various embodiments, multiple threshold number of incorrect diagnoses correspond to different diagnoses categories. For example, the threshold number of incorrect diagnoses for remediation can be higher for false negative diagnoses than false positive diagnoses. Similarly, categories corresponding to different diagnosis severities and/or rarities can have different thresholds, for example where a threshold number of more severe and/or more rare diagnoses that were inaccurate to necessitate remediation is lower than a threshold number of less severe and/or less rare diagnoses that were inaccurate.

The remediation step 1140 can include automatically updating an identified medical inference function 1105. This can include automatically retraining identified medical inference function 1105 on the same training set or on a new training set that includes new data, data with higher corresponding confidence scores, or data selected based on new training set criteria. The identified medical inference function 1105 can also be updated and/or changed based on the review data received from the client device. For example, the medical scan and expert feedback data can be added to the training set of the medical scan inference function 1105, and the medical scan inference function 1105 can be retrained on the updated training set. Alternatively or in addition, the expert user can identify additional parameters and/or rules in the expert feedback data based on the errors made by the inference function in generating the inference data 1110 for the medical scan, and these parameters and/or rules can be applied to update the medical scan inference function, for example, by updating the model type data 622 and/or model parameter data 623.

The remediation step 1140 can also include determining to split a scan category 1120 into two or more subcategories. Thus, two or more new medical scan inference functions 1105 can be created, where each new medical scan inference functions 1105 is trained on a corresponding training set that is a subset of the original training set and/or includes new medical scan data corresponding to the subcategory. This can allow medical scan inference functions 1105 to become more specialized and/or allow functions to utilize characteristics and/or discrepancies specific to the subcategory when generating inference data 1110. Similarly, a new scan category 1120 that was not previously represented by any of the medical scan inference functions 1105 can be added in the remediation step, and a new medical scan inference functions 1105 can be trained on a new set of medical scan data that corresponds to the new scan category 1120. Splitting a scan category and/or adding a scan category can be determined automatically by the medical scan diagnosing system 108 when performing the remediation step 1140, for example, based on performance score data 630. This can also be determined based on receiving instructions to split a category and/or add a new scan category from the expert user or other user of the system.

After a medical scan inference function 1105 is updated or created for the first time, the remediation step 1140 can further undergo a commissioning test, which can include rigorous testing of the medical scan inference function 1105 on a testing set, for example, based on the training parameters 620. For example, the commissioning test can be passed when the medical scan inference function 1105 generates a threshold number of correct inference data 1110 and/or the test can be passed if an overall or average discrepancy level between the inference data and the test data is below a set error threshold. The commissioning test can also evaluate efficiency, where the medical scan inference function 1105 only passes the commissioning test if it performs at or exceeds a threshold efficiency level. If the medical scan inference function 1105 fails the commissioning test, the model type and/or model parameters can be modified automatically or based on user input, and the medical scan inference function can be retested, continuing this process until the medical scan inference function 1105 passes the commissioning test.

The remediation step 1140 can include decommissioning the medical scan inference function 1105, for example, while the medical scan inference function is being retrained and/or is undergoing the commissioning test. Incoming scans to the medical scan diagnosing system 108 with a scan category 1120 corresponding to a decommissioned medical scan inference function 1105 can be sent directly to review by one or more users, for example, in conjunction with the medical scan annotator system 106. These user-reviewed medical scans and corresponding annotations can be included in an updated training set used to train the decommissioned medical scan inference function 1105 as part of the remediation step 1140. In some embodiments, previous versions of the plurality of medical scan image analysis functions can be stored in memory of the medical scan diagnosing system and/or can be determined based on the version data 640 of a medical scan inference function 1105. A previous version of a medical scan inference function 1105, such as most recent version or version with the highest performance score, can be utilized during the remediation step 1140 as an alternative to sending all medical scans to user review.

A medical scan inference function can also undergo the remediation step 1140 automatically in response to a hardware and/or software update on processing, memory, and/or other computing devices where the medical scan inference function 1105 is stored and/or performed. Different medical scan inference functions 1105 can be containerized on their own devices by utilizing a micro-service architecture, so hardware and/or software updates may only necessitate that one of the medical scan inference functions 1105 undergo the remediation step 1140 while the others remain unaffected. A medical scan inference function 1105 can also undergo the remediation step 1140 automatically in response to normal system boot-up, and/or periodically in fixed intervals. For example, in response to a scheduled or automatically detected hardware and/or software update, change, or issue, one or more medical scan inference functions 1105 affected by this hardware or software can be taken out of commission until they each pass the commissioning test. Such criteria can be indicated in the remediation criteria data 652.

The medical scan diagnosing system 108 can automatically manage usage data, subscription data, and/or billing data for the plurality of users corresponding to user usage of the system, for example, by utilizing, generating, and/or updating some or all of the subscription data of the user database. Users can pay for subscriptions to the system, which can include different subscription levels that can correspond to different costs. For example, a hospital can pay a monthly cost to automatically diagnose up to 100 medical scans per month. The hospital can choose to upgrade their subscription or pay per-scan costs for automatic diagnosing of additional scans received after the quota is reached and/or the medical scan diagnosing system 108 can automatically send medical scans received after the quota is reached to an expert user associated with the hospital. In various embodiments incentive programs can be used by the medical scan diagnosing system to encourage experts to review medical scans from different medical entities. For example, an expert can receive credit to their account and/or subscription upgrades for every medical scan reviewed, or after a threshold number of medical scans are reviewed. The incentive programs can include interactions by a user with other subsystems, for example, based on contributions made to medical scan entries via interaction with other subsystems.

FIG. 7A presents an embodiment of a medical scan image analysis system 112. A training set of medical scans used to train one more medical scan image analysis functions can be received from one or more client devices via the network and/or can be retrieved from the medical scan database 342, for example, based on training set data 621 corresponding to medical scan image analysis functions. Training set criteria, for example, identified in training parameters 620 of the medical scan image analysis function, can be utilized to automatically identify and select medical scans to be included in the training set from a plurality of available medical scans. The training set criteria can be automatically generated based on, for example, previously learned criteria, and/or training set criteria can be received via the network, for example, from an administrator of the medical scan image analysis system. The training set criteria can include a minimum training set size. The training set criteria can include data integrity requirements for medical scans in the training set such as requiring that the medical scan is assigned a truth flag 461, requiring that performance score data for a hospital and/or medical professional associated with the medical scan compares favorably to a performance score threshold, requiring that the medical scan has been reviewed by at least a threshold number of medical professionals, requiring that the medical scan and/or a diagnosis corresponding to a patient file of the medical scan is older than a threshold elapsed time period, or based on other criteria intended to insure that the medical scans and associated data in the training set is reliable enough to be considered “truth” data. The training set criteria can include longitudinal requirements such the number of required subsequent medical scans for the patient, multiple required types of additional scans for the patient, and/or other patient file requirements.

The training set criteria can include quota and/or proportion requirements for one or more medical scan classification data. For example, the training set criteria can include meeting quota and/or proportion requirements for one or more scan types and/or human body location of scans, meeting quota or proportion requirements for a number of normal medical scans and a number of medicals scans with identified abnormalities, meeting quota and/or proportion requirements for a number of medical scans with abnormalities in certain locations and/or a number of medical scans with abnormalities that meet certain size, type, or other characteristics, meeting quota and/or proportion data for a number of medical scans with certain diagnosis or certain corresponding medical codes, and/or meeting other identified quota and/or proportion data relating to metadata, patient data, or other data associated with the medical scans.

In some embodiments, multiple training sets are created to generate corresponding medical scan image analysis functions, for example, corresponding to some or all of the set of medical scan inference functions 1105. Some or all training sets can be categorized based on some or all of the scan classifier data 420 as described in conjunction with the medical scan diagnosing system 108, where medical scans are included in a training set based on their scan classifier data 420 matching the scan category of the training set. In some embodiments, the input quality assurance function 1106 or another input check step can be performed on medical scans selected for each training set to confirm that their corresponding scan classifier data 420 is correct. In some embodiments, the input quality assurance function can correspond to its own medical scan image analysis function, trained by the medical scan image analysis system, where the input quality assurance function utilizes high level computer vision technology to determine a scan category 1120 and/or to confirm the scan classifier data 420 already assigned to the medical scan.

In some embodiments, the training set will be used to create a single neural network model, or other model corresponding to model type data 622 and/or model parameter data 623 of the medical scan image analysis function that can be trained on some or all of the medical scan classification data described above and/or other metadata, patient data, or other data associated with the medical scans. In other embodiments, a plurality of training sets will be created to generate a plurality of corresponding neural network models, where the multiple training sets are divided based on some or all of the medical scan classification data described above and/or other metadata, patient data, or other data associated with the medical scans. Each of the plurality of neural network models can be generated based on the same or different learning algorithm that utilizes the same or different features of the medical scans in the corresponding one of the plurality of training sets. The medical scan classifications selected to segregate the medical scans into multiple training sets can be received via the network, for example based on input to an administrator client device from an administrator. The medical scan classifications selected to segregate the medical scans can be automatically determined by the medical scan image analysis system, for example, where an unsupervised clustering algorithm is applied to the original training set to determine appropriate medical scan classifications based on the output of the unsupervised clustering algorithm.

In embodiments where the medical scan image analysis system is used in conjunction with the medical scan diagnosing system, each of the medical scan image analysis functions associated with each neural network model can correspond to one of the plurality of neural network models generated by the medical scan image analysis system. For example, each of the plurality of neural network models can be trained on a training set classified on scan type, scan human body location, hospital or other originating entity data, machine model data, machine calibration data, contrast agent data, geographic region data, and/or other scan classifying data as discussed in conjunction with the medical scan diagnosing system. In embodiments where the training set classifiers are learned, the medical scan diagnosing system can determine which of the medical scan image analysis functions should be applied based on the learned classifying criteria used to segregate the original training set.

A computer vision-based learning algorithm used to create each neural network model can include selecting a three-dimensional subregion 1310 for each medical scan in the training set. This three-dimensional subregion 1310 can correspond to a region that is “sampled” from the entire scan that may represent a small fraction of the entire scan. Recall that a medical scan can include a plurality of ordered cross-sectional image slices. Selecting a three-dimensional subregion 1310 can be accomplished by selecting a proper image slice subset 1320 of the plurality of cross-sectional image slices from each of the plurality of medical scans, and by further selecting a two-dimensional subregion 1330 from each of the selected subset of cross-sectional image slices of the each of the medical scans. In some embodiments, the selected image slices can include one or more non-consecutive image slices and thus a plurality of disconnected three-dimensional subregions will be created. In other embodiments, the selected proper subset of the plurality of image slices correspond to a set of consecutive image slices, as to ensure that a single, connected three-dimensional subregion is selected. In some embodiments, entire scans of the training set are used to train the neural network model. In such embodiment, as used herein, the three-dimensional subregion 1310 can refer to all of the medical scan image data 410 of a medical scan.

In some embodiments, a density windowing step can be applied to the full scan or the selected three-dimensional subregion. The density windowing step can include utilizing a selected upper density value cut off and/or a selected lower density value cut off, and masking pixels with higher values than the upper density value cut off and/or masking pixels with lower values than the lower density value cut off. The upper density value cut off and/or a selected lower density value cut off can be determined based on based on the range and/or distribution of density values included in the region that includes the abnormality, and/or based on the range and/or distribution of density values associated with the abnormality itself, based on user input to a subsystem, based on display parameter data associated with the medical scan or associated with medical scans of the same type, and/or can be learned in the training step. In some embodiments, a non-linear density windowing function can be applied to alter the pixel density values, for example, to stretch or compress contrast. In some embodiments, this density windowing step can be performed as a data augmenting step, to create additional training data for a medical scan in accordance with different density windows.

Having determined the subregion training set 1315 of three-dimensional subregions 1310 corresponding to the set of full medical scans in the training set, the medical scan image analysis system can complete a training step 1352 by performing a learning algorithm on the plurality of three-dimensional subregions to generate model parameter data 1355 of a corresponding learning model. The learning model can include one or more of a neural network, an artificial neural network, a convolutional neural network, a Bayesian model, a support vector machine model, a cluster analysis model, or other supervised or unsupervised learning model. The model parameter data 1355 can generated by performing the learning algorithm 1350, and the model parameter data 1355 can be utilized to determine the corresponding medical scan image analysis functions. For example, some or all of the model parameter data 1355 can be mapped to the medical scan analysis function in the model parameter data 623 or can otherwise define the medical scan analysis function.

The training step 1352 can include creating feature vectors for each three-dimensional subregion of the training set for use by the learning algorithm 1350 to generate the model parameter data 1355. The feature vectors can include the pixel data of the three-dimensional subregions such as density values and/or grayscale values of each pixel based on a determined density window. The feature vectors can also include other features as additional input features or desired output features, such as known abnormality data such as location and/or classification data, patient history data such as risk factor data or previous medical scans, diagnosis data, responsible medical entity data, scan machinery model or calibration data, contrast agent data, medical code data, annotation data that can include raw or processed natural language text data, scan type and/or anatomical region data, or other data associated with the image, such as some or all data of a medical scan entry 352. Features can be selected based on administrator instructions received via the network and/or can be determined based on determining a feature set that reduces error in classifying error, for example, by performing a cross-validation step on multiple models created using different feature sets. The feature vector can be split into an input feature vector and output feature vector. The input feature vector can include data that will be available in subsequent medical scan input, which can include for example, the three-dimensional subregion pixel data and/or patient history data. The output feature vector can include data that will be inferred in in subsequent medical scan input and can include single output value, such as a binary value indicating whether or not the medical scan includes an abnormality or a value corresponding to one of a plurality of medical codes corresponding to the image. The output feature vector can also include multiple values which can include abnormality location and/or classification data, diagnosis data, or other output. The output feature vector can also include a determined upper density value cut off and/or lower density value cut off, for example, characterizing which pixel values were relevant to detecting and/or classifying an abnormality. Features included in the output feature vector can be selected to include features that are known in the training set, but may not be known in subsequent medical scans such as triaged scans to be diagnosed by the medical scan diagnosing system, and/or scans to be labeled by the medical scan report labeling system. The set of features in the input feature vector and output feature vector, as well as the importance of different features where each feature is assigned a corresponding weight, can also be designated in the model parameter data 1355.

Consider a medical scan image analysis function that utilizes a neural network. The neural network can include a plurality of layers, where each layer includes a plurality of neural nodes. Each node in one layer can have a connection to some or all nodes in the next layer, where each connection is defined by a weight value. Thus, the model parameter data 1355 can include a weight vector that includes weight values for every connection in the network. Alternatively or in addition, the model parameter data 1355 can include any vector or set of parameters associated with the neural network model, which can include an upper density value cut off and/or lower density value cut off used to mask some of the pixel data of an incoming image, kernel values, filter parameters, bias parameters, and/or parameters characterizing one or more of a plurality of convolution functions of the neural network model. The medical scan image analysis function can be utilized to produce the output vector as a function of the input feature vector and the model parameter data 1355 that characterizes the neural network model. In particular, the medical scan image analysis function can include performing a forward propagation step plurality of neural network layers to produce an inferred output vector based on the weight vector or other model parameter data 1355. Thus, the learning algorithm 1350 utilized in conjunction with a neural network model can include determining the model parameter data 1355 corresponding to the neural network model, for example, by populating the weight vector with optimal weights that best reduce output error.

In particular, determining the model parameter data 1355 can include utilizing a backpropagation strategy. The forward propagation algorithm can be performed on at least one input feature vector corresponding to at least one medical scan in the training set to propagate the at least one input feature vector through the plurality of neural network layers based on initial and/or default model parameter data 1355, such as an initial weight vector of initial weight values set by an administrator or chosen at random. The at least one output vector generated by performing the forward propagation algorithm on the at least one input feature vector can be compared to the corresponding at least one known output feature vector to determine an output error. Determining the output error can include, for example, computing a vector distance such as the Euclidian distance, or squared Euclidian distance, between the produced output vector and the known output vector, and/or determining an average output error such as an average Euclidian distance or squared Euclidian distance if multiple input feature vectors were employed. Next, gradient descent can be performed to determine an updated weight vector based on the output error or average output error. This gradient descent step can include computing partial derivatives for the error with respect to each weight, or other parameter in the model parameter data 1355, at each layer starting with the output layer. Chain rule can be utilized to iteratively compute the gradient with respect to each weight or parameter at each previous layer until all weight's gradients are computed. Next updated weights, or other parameters in the model parameter data 1355, are generated by updating each weight based on its corresponding calculated gradient. This process can be repeated on at least one input feature vector, which can include the same or different at least one feature vector used in the previous iteration, based on the updated weight vector and/or other updated parameters in the model parameter data 1355 to create a new updated weight vector and/or other new updated parameters in the model parameter data 1355. This process can continue to repeat until the output error converges, the output error is within a certain error threshold, or another criterion is reached to determine the most recently updated weight vector and/or other model parameter data 1355 is optimal or otherwise determined for selection.

Having determined the medical scan neural network and its final other model parameter data 1355, an inference step 1354 can be performed on new medical scans to produce inference data 1370, such as inferred output vectors, as shown in FIG. 7B. The inference step can include performing the forward propagation algorithm to propagate an input feature vector through a plurality of neural network layers based on the final model parameter data 1355, such as the weight values of the final weight vector, to produce the inference data. This inference step 1354 can correspond to performing the medical scan image analysis function, as defined by the final model parameter data 1355, on new medical scans to generate the inference data 1370, for example, in conjunction with the medical scan diagnosing system 108 to generate inferred diagnosis data or other selected output data for triaged medical scans based on its corresponding the input feature vector.

The inference step 1354 can include applying the density windowing step to new medical scans. Density window cut off values and/or a non-linear density windowing function that are learned can be automatically applied when performing the inference step. For example, if the training step 1352 was used to determine optimal upper density value cut off and/or lower density value cut off values to designate an optimal density window, the inference step 1354 can include masking pixels of incoming scans that fall outside of this determined density window before applying the forward propagation algorithm. As another example, if learned parameters of one or more convolutional functions correspond to the optimal upper density value cut off and/or lower density value cut off values, the density windowing step is inherently applied when the forward propagation algorithm is performed on the new medical scans.

In some embodiments where a medical scan analysis function is defined by model parameter data 1355 corresponding to a neutral network model, the neural network model can be a fully convolutional neural network. In such embodiments, only convolution functions are performed to propagate the input feature vector through the layers of the neural network in the forward propagation algorithm. This enables the medical scan image analysis functions to process input feature vectors of any size. For example, as discussed herein, the pixel data corresponding to the three-dimensional subregions is utilized input to the forward propagation algorithm when the training step 1352 is employed to populate the weight vector and/or other model parameter data 1355. However, when performing the forward propagation algorithm in the inference step 1354, the pixel data of full medical scans can be utilized as input, allowing the entire scan to be processed to detect and/or classify abnormalities, or otherwise generate the inference data 1370. This may be a preferred embodiment over other embodiments where new scans must also be sampled by selecting a three-dimensional subregions and/or other embodiments where the inference step requires “piecing together” inference data 1370 corresponding to multiple three-dimensional subregions processed separately.

The inferred output vector of the inference data 1370 can include a plurality of abnormality probabilities mapped to a pixel location of each of a plurality of cross-sectional image slices of the new medical scan. For example, the inferred output vector can indicate a set of probability matrices 1371, where each matrix in the set corresponds to one of the plurality of image slices of the medical scan, where each matrix is a size corresponding to the number of pixels in each image slice, where each cell of each matrix corresponds to a pixel of the corresponding image slice, whose value is the abnormality probability of the corresponding pixel.

A detection step 1372 can include determining if an abnormality is present in the medical scan based on the plurality of abnormality probabilities. Determining if an abnormality is present can include, for example, determining that a cluster of pixels in the same region of the medical scan correspond to high abnormality probabilities, for example, where a threshold proportion of abnormality probabilities must meet or exceed a threshold abnormality probability, where an average abnormality probability of pixels in the region must meet or exceed a threshold abnormality probability, where the region that includes the cluster of pixels must be at least a certain size, etc. Determining if an abnormality is present can also include calculating a confidence score based on the abnormality probabilities and/or other data corresponding to the medical scan such as patient history data. The location of the detected abnormality can be determined in the detection step 1372 based on the location of the pixels with the high abnormality probabilities. The detection step can further include determining an abnormality region 1373, such as a two-dimensional subregion on one or more image slices that includes some or all of the abnormality. The abnormality region 1373 determined in the detection step 1372 can be mapped to the medical scan to populate some or all of the abnormality location data 443 for use by one or more other subsystems 101 and/or client devices 120. Furthermore, determining whether or not an abnormality exists in the detection step 1372 can be used to populate some or all of the diagnosis data 440 of the medical scan, for example, to indicate that the scan is normal or contains an abnormality in the diagnosis data 440.

An abnormality classification step 1374 can be performed on a medical scan in response to determining an abnormality is present. Classification data 1375 corresponding to one or more classification categories such as abnormality size, volume, pre-post contract, doubling time, calcification, components, smoothness, texture, diagnosis data, one or more medical codes, a malignancy rating such as a Lung-RADS score, or other classifying data as described herein can be determined based on the detected abnormality. The classification data 1375 generated by the abnormality classification step 1374 can be mapped to the medical scan to populate some or all of the abnormality classification data 445 of the corresponding abnormality classifier categories 444 and/or abnormality pattern categories 446 and/or to determine one or more medical codes 447 of the medical scan. The abnormality classification step 1374 can include performing an abnormality classification function on the full medical scan, or the abnormality region 1373 determined in the detection step 1372. The abnormality classification function can be based on another model trained on abnormality data such as a support vector machine model, another neural network model, or any supervised classification model trained on medical scans, or portions of medical scans, that include known abnormality classifying data to generate inference data for some or all of the classification categories. For example, the abnormality classification function can include another medical scan analysis function. Classification data 1375 in each of a plurality of classification categories can also be assigned their own calculated confidence score, which can also be generated by utilizing the abnormality classification function. Output to the abnormality classification function can also include at least one identified similar medical scan and/or at least one identified similar cropped image, for example, based on the training data. The abnormality classification step can also be included in the inference step 1354, where the inferred output vector or other inference data 1370 of the medical scan image analysis function includes the classification data 1375.

The abnormality classification function can be trained on full medical scans and/or one or more cropped or full selected image slices from medical scans that contain an abnormality. For example, the abnormality classification function can be trained on a set of two-dimensional cropped slices that include abnormalities. The selected image slices and/or the cropped region in each selected image slice for each scan in the training set can be automatically selected based upon the known location of the abnormality. Input to the abnormality classification function can include the full medical scan, one or more selected full image slices, and/or one or more selected image slices cropped based on a selected region. Thus, the abnormality classification step can include automatically selecting one or more image slices that include the detected abnormality. The slice selection can include selecting the center slice in a set of consecutive slices that are determined to include the abnormality or selecting a slice that has the largest cross-section of the abnormality, or selecting one or more slices based on other criteria. The abnormality classification step can also include automatically generating one or more cropped two-dimensional images corresponding to the one or more of the selected image slices based on an automatically selected region that includes the abnormality.

Input to the abnormality classification function can also include other data associated with the medical scan, including patient history, risk factors, or other metadata. The abnormality classification step can also include determining some or all of the characteristics based on data of the medical scan itself. For example, the abnormality size and volume can be determined based on a number of pixels determined to be part of the detected abnormality. Other classifiers such as abnormality texture and/or smoothness can be determined by performing one or more other preprocessing functions on the image specifically designed to characterize such features. Such preprocessed characteristics can be included in the input to the abnormality classification function to the more difficult task of assigning a medical code or generating other diagnosis data. The training data can also be preprocessed to include such preprocessed features.

A similar scan identification step 1376 can also be performed on a medical scan with a detected abnormality and/or can be performed on the abnormality region 1373 determined in the detection step 1372. The similar scan identification step 1376 can include generating similar abnormality data 1377, for example, by identifying one or more similar medical scans or one or more similar cropped two-dimensional images from a database of medical scans and/or database of cropped two-dimensional images. Similar medical scans and/or cropped images can include medical scans or cropped images that are visually similar, medical scans or cropped images that have known abnormalities in a similar location to an inferred abnormality location of the given medical scan, medical scans that have known abnormalities with similar characteristics to inferred characteristics of an abnormality in the given scan, medical scans with similar patient history and/or similar risk factors, or some combination of these factors and/or other known and/or inferred factors. The similar abnormality data 1377 can be mapped to the medical scan to populate some or all of its corresponding similar scan data 480 for use by one or more other subsystems 101 and/or client devices 120.

The similar scans identification step 1376 can include performing a scan similarity algorithm, which can include generating a feature vector for the given medical scan and for medical scans in the set of medical scans, where the feature vector can be generated based on quantitative and/or category based visual features, inferred features, abnormality location and/or characteristics such as the predetermined size and/or volume, patient history and/or risk factor features, or other known or inferred features. A medical scan similarity analysis function can be applied to the feature vector of the given medical scan and one or more feature vectors of medical scans in the set. The medical scan similarity analysis function can include computing a similarity distance such as the Euclidian distance between the feature vectors, and assigning the similarity distance to the corresponding medical scan in the set. Similar medical scans can be identified based on determining one or more medical scans in the set with a smallest computed similarity distance, based on ranking medical scans in the set based on the computed similarity distances and identifying a designated number of top ranked medical scans, and/or based on determining if a similarity distance between the given medical scan and a medical scan in the set is smaller than a similarity threshold. Similar medical scans can also be identified based on determining medical scans in a database that mapped to a medical code that matches the medical code of the medical scan, or mapped to other matching classifying data. A set of identified similar medical scans can also be filtered based on other inputted or automatically generated criteria, where for example only medical scans with reliable diagnosis data or rich patient reports, medical scans with corresponding with longitudinal data in the patient file such as multiple subsequent scans taken at later dates, medical scans with patient data that corresponds to risk factors of the given patient, or other identified criteria, where only a subset of scans that compare favorably to the criteria are selected from the set and/or only a highest ranked single scan or subset of scans are selected from the set, where the ranking is automatically computed based on the criteria. Filtering the similar scans in this fashion can include calculating, or can be based on previously calculated, one or more scores as discussed herein. For example, the ranking can be based on a longitudinal quality score, such as the longitudinal quality score 434, which can be calculated for an identified medical scan based on a number of subsequent and/or previous scans for the patient. Alternatively or in addition, the ranking can be based on a confidence score associated with diagnosis data of the scan, such as confidence score data 460, based on performance score data associated with a user or medical entity associated with the scan, based on an amount of patient history data or data in the medical scan entry 352, or other quality factors. The identified similar medical scans can be filtered based on ranking the scans based on their quality score and/or based on comparing their quality score to a quality score threshold. In some embodiments, a longitudinal threshold must be reached, and only scans that compare favorably to the longitudinal threshold will be selected. For example, only scans with at least three scans on file for the patient and final biopsy data will be included.

In some embodiments, the similarity algorithm can be utilized in addition to or instead of the trained abnormality classification function to determine some or all of the inferred classification data 1375 of the medical scan, based on the classification data such as abnormality classification data 445 or other diagnosis data 440 mapped to one or more of the identified similar scans. In other embodiments, the similarity algorithm is merely used to identify similar scans for review by medical professionals to aid in review, diagnosis, and/or generating medical reports for the medical image.

A display parameter step 1378 can be performed based on the detection and/or classification of the abnormality. The display parameter step can include generating display parameter data 1379, which can include parameters that can be used by an interactive interface to best display each abnormality. The same or different display parameters can be generated for each abnormality. The display parameter data generated in the display parameter step 1378 can be mapped to the medical scan to populate some or all of its corresponding display parameter data 470 for use by one or more other subsystems 101 and/or client devices 120.

Performing the display parameter step 1378 can include selecting one or more image slices that include the abnormality by determining the one or more image slices that include the abnormality and/or determining one or more image slices that has a most optimal two-dimensional view of the abnormality, for example by selecting the center slice in a set of consecutive slices that are determined to include the abnormality, selecting a slice that has the largest cross-section of the abnormality, selecting a slice that includes a two-dimensional image of the abnormality that is most similar to a selected most similar two-dimensional-image, selecting the slice that was used as input to the abnormality classification step and/or similar scan identification step, or based on other criteria. This can also include automatically cropping one or more selected image slices based on an identified region that includes the abnormality. This can also select an ideal Hounsfield window that best displays the abnormality. This can also include selecting other display parameters based on data generated by the medical scan interface evaluating system and based on the medical scan.

FIGS. 8A-8F illustrate embodiments of a medical picture archive integration system 2600. The medical picture archive integration system 2600 can provide integration support for a medical picture archive system 2620, such as a PACS that stores medical scans. The medical picture archive integration system 2600 can utilize model parameters received from a central server system 2640 via a network 2630 to perform an inference function on de-identified medical scans of medical scans received from the medical picture archive system 2620. The annotation data produced by performing the inference function can be transmitted back to the medical picture archive system. Furthermore, the annotation data and/or de-identified medical scans can be sent to the central server system 2640, and the central server system can train on this information to produce new and/or updated model parameters for transmission back to the medical picture archive integration system 2600 for use on subsequently received medical scans.

In various embodiments, medical picture archive integration system 2600 includes a de-identification system that includes a first memory designated for protected health information (PHI), operable to perform a de-identification function on a DICOM image, received from a medical picture archive system, to identify at least one patient identifier and generate a de-identified medical scan that does not include the at least one patient identifier. The medical picture archive integration system further includes a de-identified image storage system that stores the de-identified medical scan in a second memory that is separate from the first memory, and an annotating system, operable to utilize model parameters received from a central server to perform an inference function on the de-identified medical scan, retrieved from the second memory to generate annotation data for transmission to the medical picture archive system as an annotated DICOM file.

The first memory and the second memory can be implemented by utilizing separate storage systems: the first memory can be implemented by a first storage system designated for PHI storage, and the second memory can be implemented by a second storage system designated for storage of de-identified data. The first storage system can be protected from access by the annotating system, while the second storage system can be accessible by the annotating system. The medical picture archive integration system 2600 can be operable to perform the de-identification function on data in first storage system to generate de-identified data. The de-identified data can then be stored in the second storage system for access by the annotating system. The first and second storage systems can be physically separate, each utilizing at least one of their own, separate memory devices. Alternatively, the first and second storage systems can be virtually separate, where data is stored in separate virtual memory locations on the same set of memory devices. Firewalls, virtual machines, and/or other protected containerization can be utilized to enforce the separation of data in each storage system, to protect the first storage system from access by the annotating system and/or from other unauthorized access, and/or to ensure that only data of the first storage system that has been properly de-identified through application of the de-identification function can be stored in the second storage system.

As shown in FIG. 8A, the medical picture archive system 2620 can receive image data from a plurality of modality machines 2622, such as CT machines, Mill machines, x-ray machines, and/or other medical imaging machines that produce medical scans. The medical picture archive system 2620 can store this image data in a DICOM image format and/or can store the image data in a plurality of medical scan entries 352 as described in conjunction with some or all of the attributes described in conjunction with FIGS. 4A and 4B. While “DICOM image” will be used herein to refer to medical scans stored by the medical picture archive system 2620, the medical picture archive integration system 2600 can provide integration support for medical picture archive systems 2620 that store medical scans in other formats.

The medical picture archive integration system 2600 can include a receiver 2602 and a transmitter 2604, operable to transmit and receive data from the medical picture archive system 2620, respectively. For example, the receiver 2602 and transmitter 2604 can be configured to receive and transmit data, respectively, in accordance with a DICOM communication protocol and/or another communication protocol recognized by the medical image archive system 2620. The receiver can receive DICOM images from the medical picture archive system 2620. The transmitter 2604 can send annotated DICOM files to the medical picture archive system 2620.

DICOM images received via receiver 2602 can be sent directly to a de-identification system 2608. The de-identification system 2608 can be operable to perform a de-identification function on the first DICOM image to identify at least one patient identifier in the DICOM image, and to generate a de-identified medical scan that does not include the identified at least one patient identifier. As used herein, a patient identifier can include any patient identifying data in the image data, header, and/or metadata of a medical scan, such as a patient ID number or other unique patient identifier, an accession number, a service-object pair (SOP) instance unique identifier (UID) field, scan date and/or time that can be used to determine the identity of the patient that was scanned at that date and/or time, and/or other private data corresponding to the patient, doctor, or hospital. In some embodiments, the de-identified medical scan is still in a DICOM image format. For example, a duplicate DICOM image that does not include the patient identifiers can be generated, and/or the original DICOM image can be altered such that the patient identifiers of the new DICOM image are masked, obfuscated, removed, replaced with a custom fiducial, and/or otherwise anonymized. In other embodiments, the de-identified medical scan is formatted in accordance with a different image format and/or different data format that does not include the identifying information. In some embodiments, other private information, for example, associated with a particular doctor or other medical professional, can be identified and anonymized as well.

Some patient identifying information can be included in a DICOM header of the DICOM image, for example, in designated fields for patient identifiers. These corresponding fields can be anonymized within the corresponding DICOM header field. Other patient identifying information can be included in the image itself, such as in medical scan image data 410. For example, the image data can include a patient name or other identifier that was handwritten on a hard copy of the image before the image was digitized. As another example, a hospital administered armband or other visual patient information in the vicinity of the patient may have been captured in the image itself. A computer vision model can detect the presence of these identifiers for anonymization, for example, where a new DICOM image includes a fiducial image that covers the identifying portion of the original DICOM image. In some embodiments, patient information identified in the DICOM header can be utilized to detect corresponding patient information in the image itself. For example, a patient name extracted from the DICOM header before anonymization can be used to search for the patient name in the image and/or to detect a location of the image that includes the patient name. In some embodiments, the de-identification system 2608 is implemented by the de-identification system discussed in conjunction with FIGS. 10A, 10B and 11, and/or utilizes functions and/or operations discussed in conjunction with FIGS. 10A, 10B and 11.

The de-identified medical scan can be stored in de-identified image storage system 2610 and the annotating system 2612 can access the de-identified medical scan from the de-identified image storage system 2610 for processing. The de-identified storage system can archive a plurality of de-identified DICOM images and/or can serve as temporary storage for the de-identified medical scan until processing of the de-identified medical scan by the annotating system 2612 is complete. The annotating system 2612 can generate annotation data by performing an inference function on the de-identified medical scan, utilizing the model parameters received from the central server system 2640. The annotation data can correspond to some or all of the diagnosis data 440 as discussed in conjunction with FIGS. 4A and 4B. In come embodiments, the annotating system 2612 can utilize the model parameters to perform inference step 1354, the detection step 1372, the abnormality classification step 1374, the similar scan identification step 1376, and/or the display parameter step 1378 of the medical scan image analysis system 112, as discussed in conjunction with FIG. 7B, on de-identified medical scans received from the medical picture archive system 2620.

In some embodiments, model parameters for a plurality of inference functions can be received from the central server system 2640, for example, where each inference function corresponds to one of a set of different scan categories. Each scan category can correspond to a unique combination of one or a plurality of scan modalities, one of a plurality of anatomical regions, and/or other scan classifier data 420. For example, a first inference function can be trained on and intended for de-identified medical scans corresponding chest CT scans, and a second inference function can be trained on and intended for de-identified medical scans corresponding to head Mill scans. The annotating system can select one of the set of inference functions based on determining the scan category of the DICOM image, indicated in the de-identified medical scan, and selecting the inference function that corresponds to the determined scan category.

To ensure that scans received from the medical picture archive system 2620 match the set of scan categories for which the annotating system is operable to perform a corresponding inference function, the transmitter can transmit requests, such as DICOM queries, indicating image type parameters such as parameters corresponding to scan classifier data 420, for example indicating one or more scan modalities, one or more anatomical regions, and/or other parameters. For example, the request can indicate that all incoming scans that match the set of scan categories corresponding to a set of inference functions the annotating system 2612 for which the annotating system has obtained model parameters from the central server system 2640 and is operable to perform.

Once the annotation data is generated by performing the selected inference function, the annotating system 2612 can generate an annotated DICOM file for transmission to the medical image archive system 2620 for storage. The annotated DICOM file can include some or all of the fields of the diagnosis data 440 and/or abnormality annotation data 442 of FIGS. 4A and 4B. The annotated DICOM file can include scan overlay data, providing location data of an identified abnormality and/or display data that can be used in conjunction with the original DICOM image to indicate the abnormality visually in the DICOM image and/or to otherwise visually present the annotation data, for example, for use with the medical scan assisted review system 102. For example, a DICOM presentation state file can be generated to indicate the location of an abnormality identified in the de-identified medical scan. The DICOM presentation state file can include an identifier of the original DICOM image, for example, in metadata of the DICOM presentation state file, to link the annotation data to the original DICOM image. In other embodiments, a full, duplicate DICOM image is generated that includes the annotation data with an identifier linking this duplicate annotated DICOM image to the original DICOM image.

The identifier linking the annotated DICOM file to the original DICOM image can be extracted from the original DICOM file by the de-identification system 2608, thus enabling the medical picture archive system 2620 to link the annotated DICOM file to the original DICOM image in its storage. For example, the de-identified medical scan can include an identifier that links the de-identified medical scan to the original DICOM file, but does not link the de-identified medical scan to a patient identifier or other private data.

In some embodiments, generating the annotated DICOM file includes altering one or more fields of the original DICOM header. For example, standardized header formatting function parameters can be received from the central server system and can be utilized by the annotating system to alter the original DICOM header to match a standardized DICOM header format. The standardized header formatting function can be trained in a similar fashion to other medical scan analysis functions discussed herein and/or can be characterized by some or all fields of a medical scan analysis function entry 356. The annotating system can perform the standardized header formatting function on a de-identified medical scan to generate a new, standardized DICOM header for the medical scan to be sent back to the medical picture archive system 2620 in the annotated DICOM file and/or to replace the header of the original DICOM file. The standardized header formatting function can be run in addition to other inference functions utilized to generate annotation data. In other embodiments, the medical picture archive integration system 2600 is implemented primarily for header standardization for medical scans stored by the medical picture archive system 2620. In such embodiments, only the standardized header formatting function is performed on the de-identified data to generate a modified DICOM header for the original DICOM image, but the de-identified medical scan is not annotated.

In some embodiments of header standardization, the annotation system can store a set of acceptable, standardized entries for some or all of the DICOM header fields, and can select one of the set of acceptable, standardized entries in populating one or more fields of the new DICOM header for the annotated DICOM file. For example, each of the set of scan categories determined by the annotating system can correspond to a standardized entry of one or more fields of the DICOM header. The new DICOM header can thus be populated based on the determined scan category.

In some embodiments, each of the set of standardized entries can be mapped to a set of related, non-standardized entries, such as entries in a different order, commonly misspelled entries, or other similar entries that do not follow a standardized format. For example, one of the set of acceptable, standardized entries for a field corresponding to a scan category can include “Chest CT”, which can be mapped to a set of similar, non-standardized entries which can include “CT chest”, “computerized topography CT”, and/or other entries that are not standardized. In such embodiments, the annotating system can determine the original DICOM header is one of the similar non-standardized entries, and can select the mapped, standardized entry as the entry for the modified DICOM header. In other embodiments, the image data itself and/or or other header data can be utilized by the annotation system to determine a standardized field. For example, an input quality assurance function 1106 can be trained by the central server system and sent to the annotating system to determine one or more appropriate scan classifier fields, or one or more other DICOM header fields, based on the image data or other data of the de-identified medical scan. One or more standardized labels can be assigned to corresponding fields of the modified DICOM header based on the one or more fields determined by the input quality assurance function.

In some embodiments, the DICOM header is modified based on the annotation data generated in performing the inference function. In particular, a DICOM priority header field can be generated and/or modified automatically based on the severity and/or time-sensitivity of the abnormalities detected in performing the inference function. For example, a DICOM priority header field can be changed from a low priority to a high priority in response to annotation data indicating a brain bleed in the de-identified medical scan of a DICOM image corresponding to a head CT scan, and a new DICOM header that includes the high priority DICOM priority header field can be sent back to the medical picture archive system 2620 to replace or otherwise be mapped to the original DICOM image of the head CT scan.

In various embodiments, the medical picture archive system 2620 is disconnected from network 2630, for example, to comply with requirements regarding Protected Health Information (PHI), such as patient identifiers and other private patient information included in the DICOM images and/or otherwise stored by the medical picture archive system 2620. The medical picture archive integration system 2600 can enable processing of DICOM images while still protecting private patient information by first de-identifying DICOM data by utilizing de-identification system 2608. The de-identification system 2608 can utilize designated processors and memory of the medical picture archive integration system, for example, designated for PHI. The de-identification system 2608 can be decoupled from the network 2630 to prevent the DICOM images that still include patient identifiers from being accessed via the network 2630. For example, as shown in FIG. 8A, the de-identification system 2608 is not connected to network interface 2606. Furthermore, only the de-identification system 2608 has access to the original DICOM files received from the medical picture archive system 2620 via receiver 2602. The de-identified image storage system 2610 and annotating system 2612, as they are connected to network 2630 via network interface 2606, only store and have access to the de-identified medical scan produced by the de-identification system 2608.

This containerization that separates the de-identification system 2608 from the de-identified image storage system 2610 and the annotating system 2612 is further illustrated in FIG. 8B, which presents an embodiment of the medical picture archive integration system 2600. The de-identification system 2608 can include its own designated memory 2654 and processing system 2652, connected to receiver 2602 via bus 2659. For example, this memory 2654 and processing system 2652 can be designated for PHI, and can adhere to requirements for handling PHI. The memory 2654 can store executable instructions that, when executed by the processing system 2652, enable the de-identification system to perform the de-identification function on DICOM images received via receiver 2602 of the de-identification system. The incoming DICOM images can be temporarily stored in memory 2654 for processing, and patient identifiers detected in performing the de-identification function can be temporarily stored in memory 2654 to undergo anonymization. Interface 2655 can transmit the de-identified medical scan to interface 2661 for use by the de-identified image storage system 2610 and the annotating system 2612. Interface 2655 can be protected from transmitting original DICOM files and can be designated for transmission of de-identified medical scan only.

Bus 2669 connects interface 2661, as well as transmitter 2604 and network interface 2606, to the de-identified image storage system 2610 and the annotating system 2612. The de-identified image storage system 2610 and annotating system 2612 can utilize separate processors and memory, or can utilize shared processors and/or memory. For example, the de-identified image storage system 2610 can serve as temporary memory of the annotating system 2612 as de-identified images are received and processed to generate annotation data.

As depicted in FIG. 8B, the de-identified image storage system 2610 can include memory 2674 that can temporarily store incoming de-identified medical scans as it undergoes processing by the annotating system 2612 and/or can archive a plurality of de-identified medical scans corresponding to a plurality of DICOM images received by the medical picture archive integration system 2600. The annotating system 2612 can include a memory 2684 that stores executable instructions that, when executed by processing system 2682, cause the annotating system 2612 perform a first inference function on de-identified medical scan to generate annotation data by utilizing the model parameters received via interface 2606, and to generate an annotated DICOM file based on the annotation data for transmission via transmitter 2604. The model parameters can be stored in memory 2684, and can include model parameters for a plurality of inference functions, for example, corresponding to a set of different scan categories.

The medical picture archive integration system can be an onsite system, installed at a first geographic site, such as a hospital or other medical entity that is affiliated with the medical picture archive system 2620. The hospital or other medical entity can further be responsible for the PHI of the de-identification system, for example, where the memory 2654 and processing system 2652 are owned by, maintained by, and/or otherwise affiliated with the hospital or other medical entity. The central server system 2640 can be located at a second, separate geographic site that is not affiliated with the hospital or other medical entity and/or at a separate geographic site that is not affiliated with the medical picture archive system 2620. The central server system 2640 can be a server configured to be outside the network firewall and/or out outside the physical security of the hospital or other medical entity or otherwise not covered by the particular administrative, physical and technical safeguards of the hospital or other medical entity.

FIG. 8C further illustrates how model parameters can be updated over time to improve existing inference functions and/or to add new inference functions, for example corresponding to new scan categories. In particular, the some or all of the de-identified medical scans generated by the de-identification system 2608 can be transmitted back to the central server system, and the central server system 2640 can train on this data to improve existing models by producing updated model parameters of an existing inference function and/or to generate new models, for example, corresponding to new scan categories, by producing new model parameters for new inference functions. For example, the central server system 2640 can produce updated and/or new model parameters by performing the training step 1352 of the medical scan image analysis system 112, as discussed in conjunction with FIG. 7A, on a plurality of de-identified medical scans received from the medical picture archive integration system 2600.

The image type parameters can be determined by the central server system to dictate characteristics of the set of de-identified medical scans to be received to train and/or retrain the model. For example, the image type parameters can correspond to one or more scan categories, can indicate scan classifier data 420, can indicate one or more scan modalities, one or more anatomical regions, a date range, and/or other parameters. The image type parameters can be determined by the central server system based on training parameters 620 determined for the corresponding inference function to be trained, and/or based on characteristics of a new and/or existing scan category corresponding to the inference function to be trained. The image type parameters can be sent to the medical picture archive integration system 2600, and a request such as a DICOM query can be sent to the medical picture archive system 2620, via transmitter 2604, that indicates the image type parameters. For example, the processing system 2682 can be utilized to generate the DICOM query based on the image type parameters received from the central server system 2640. The medical picture archive system can automatically transmit one or more DICOM images to the medical picture archive integration system in response to determining that the one or more DICOM images compares favorably to the image type parameters. The DICOM images received in response can be de-identified by the de-identification system 2608. In some embodiments, the de-identified medical scans can be transmitted directly to the central server system 2640, for example, without generating annotation data.

The central server system can generate the new and/or updated model parameters by training on the received set of de-identified medical scans, and can transmit the new and/or updated model parameters to the de-identified storage system. If the model parameters correspond to a new inference function for a new scan category, the medical picture archive integration system 2600 can generate a request, such as a DICOM query, for transmission to the medical picture archive system indicating that incoming scans corresponding to image type parameters corresponding to the new scan category be sent to the medical picture archive integration system. The annotating system can update the set of inference functions to include the new inference function, and the annotating system can select the new inference function from the set of inference functions for subsequently generated de-identified medical scans by the de-identification system by determining each of these de-identified medical scans indicate the corresponding DICOM image corresponds to the new scan category. The new model parameters can be utilized to perform the new inference function on each of these de-identified medical scans to generate corresponding annotation data, and an annotated DICOM file corresponding to each of these de-identified medical scans can be generated for transmission to the medical picture archive system via the transmitter.

In some embodiments, the central server system 2640 receives a plurality of de-identified medical scans from a plurality of medical picture archive integration system 2600, for example, each installed at a plurality of different hospitals or other medical entities, via the network 2630. The central server system can generate training sets by integrating de-identified medical scans from some or all of the plurality of medical picture archive integration systems 2600 to train one or more inference functions and generate model parameters. The plurality of medical picture archive integration systems 2600 can utilize the same set of inference functions or different sets of inference functions. In some embodiments, the set of inference functions utilized by the each of the plurality of medical picture archive systems 2620 are trained on different sets of training data. For example, the different sets of training data can correspond to the set of de-identified medical scans received from the corresponding medical picture archive integration system 2600.

In some embodiments, the medical scan diagnosing system 108 can be utilized to implement the annotating system 2612, where the corresponding subsystem processing device 235 and subsystem memory device 245 of the medical scan diagnosing system 108 are utilized to implement the processing system 2682 and the memory 2684, respectively. Rather than receiving the medical scans via the network 150 as discussed in conjunction with FIG. 6A, the medical scan diagnosing system 108 can perform a selected medical scan inference function 1105 on an incoming de-identified medical scan generated by the de-identification system 2608 and/or retrieved from the de-identified image storage system 2610. Memory 2684 can store the set of medical scan inference functions 1105, each corresponding to a scan category 1120, where the inference function is selected from the set based on determining the scan category of the de-identified medical scan and selecting the corresponding inference function. The processing system 2682 can perform the selected inference function 1105 to generate the inference data 1110, which can be further utilized by the annotating system 2612 to generate the annotated DICOM file for transmission back to the medical picture archive system 2620. New medical scan inference functions 1105 can be added to the set when corresponding model parameters are received from the central server system. The remediation step 1140 can be performed locally by the annotating system 2612 and/or can be performed by the central server system 2640 by utilizing one or more de-identified medical scans and corresponding annotation data sent to the central server system 2640. Updated model parameters can be generated by the central server system 2640 and sent to the medical picture archive integration system 2600 as a result of performing the remediation step 1140.

The central server system 2640 can be implemented by utilizing one or more of the medical scan subsystems 101, such as the medical scan image analysis system 112 and/or the medical scan diagnosing system 108, to produce model parameters for one or more inference functions. The central server system can store or otherwise communicate with a medical scan database 342 that includes the de-identified medical scans and/or annotation data received from one or more medical picture archive integration systems 2600. Some or all entries of the medical scan database 342 can be utilized to as training data to produce model parameters for one or more inference functions. These entries of the medical scan database 342 can be utilized by other subsystems 101 as discussed herein. For example, other subsystems 101 can utilize the central server system 2640 to fetch medical scans and/or corresponding annotation data that meet specified criteria. The central server system 2640 can query the medical picture archive integration system 2600 based on this criteria, and can receive de-identified medical scans and/or annotation data in response. This can be sent to the requesting subsystem 101 directly and/or can be added to the medical scan database 342 or another database of the database storage system 140 for access by the requesting subsystem 101.

Alternatively or in addition, the central server system 2640 can store or otherwise communicate with a user database 344 storing user profile entries corresponding to each of a plurality of medical entities that each utilize a corresponding one of a plurality of medical picture archive integration systems 2600. For example, basic user data corresponding to the medical entity can be stored as basic user data, a number of scans or other consumption information indicating usage of one or more inference functions by corresponding medical picture archive integration system can be stored as consumption usage data, and/or a number of scans or other contribution information indicating de-identified scans sent to the central server system as training data can be stored as contribution usage data. The user profile entry can also include inference function data, for example, with a list of model parameters or function identifiers, such as medical scan analysis function identifiers 357, of inference functions currently utilized by the corresponding medical picture archive integration system 2600. These entries of the user database 344 can be utilized by other subsystems 101 as discussed herein.

Alternatively or in addition, the central server system 2640 can store or otherwise communicate with a medical scan analysis function database 346 to store model parameters, training data, or other information for one or more inference functions as medical scan analysis function entries 356. In some embodiments, model parameter data 623 can indicate the model parameters and function classifier data 610 can indicate the scan category of inference function entries. In some embodiments, the medical scan analysis function entry 356 can further include usage identifying information indicating a medical picture archive integration system identifier, medical entity identifier, and/or otherwise indicating which medical archive integration systems and/or medical entities have received the corresponding model parameters to utilize the inference function corresponding to the medical scan analysis function entry 356. These entries of the medical scan analysis function database 346 can be utilized by other subsystems 101 as discussed herein.

In some embodiments, the de-identification function is a medical scan analysis function, for example, with a corresponding medical scan analysis function entry 356 in the medical scan analysis function database 346. In some embodiments, the de-identification function is trained by the central server system 2640. For example, the central server system 2640 can send de-identification function parameters to the medical picture archive integration system 2600 for use by the de-identification system 2608. In embodiments with a plurality of medical picture archive integration systems 2600, each of the plurality of medical picture archive integration systems 2600 can utilize the same or different de-identification functions. In some embodiments, the de-identification function utilized by the each of the plurality of medical picture archive integration systems 2600 are trained on different sets of training data. For example, the different sets of training data can correspond to each different set of de-identified medical scans received from each corresponding medical picture archive integration system 2600.

In some embodiments, as illustrated in FIGS. 8D-8F, the medical picture archive integration system 2600 can further communicate with a report database 2625, such as a Radiology Information System (RIS), that includes a plurality of medical reports corresponding to the DICOM images stored by the medical picture archive system 2620.

As shown in FIG. 8D, the medical picture archive integration system 2600 can further include a receiver 2603 that receives report data, corresponding to the DICOM image, from report database 2625. The report database 2625 can be affiliated with the medical picture archive system 2620 and can store report data corresponding to DICOM images stored in the medical picture archive system. The report data of report database 2625 can include PHI, and the report database 2625 can thus be disconnected from network 2630.

The report data can include natural language text, for example, generated by a radiologist that reviewed the corresponding DICOM image. The report data can be used to generate the de-identified medical scan, for example, where the de-identification system 2608 performs a natural language analysis function on the report data to identify patient identifying text in the report data. The de-identification system 2608 can utilize this patient identifying text to detect matching patient identifiers in the DICOM image to identify the patient identifiers of the DICOM image and generate the de-identified medical scan. In some embodiments, the report data can be de-identified by obfuscating, hashing, removing, replacing with a fiducial, or otherwise anonymizing the identified patient identifying text to generate de-identified report data.

The de-identified report data can be utilized by the annotating system 2612, for example, in conjunction with the DICOM image, to generate the annotation data. For example, the annotating system 2612 can perform a natural language analysis function on the de-identified natural language text of the report data to generate some or all of the annotation data. In some embodiments, the de-identified report data is sent to the central server system, for example, to be used as training data for inference functions, for natural language analysis functions, for other medical scan analysis functions, and/or for use by at least one other subsystem 101. For example, other subsystems 101 can utilize the central server system 2640 to fetch medical reports that correspond to particular medical scans or otherwise meet specified criteria. The central server system 2640 can query the medical picture archive integration system 2600 based on this criteria, and can receive de-identified medical reports in response. This can be sent to the requesting subsystem 101 directly, can be added to the medical scan database 342, a de-identified report database, or another database of the database storage system 140 for access by the requesting subsystem 101.

In some embodiments the medical picture archive integration system 2600 can query the report database 2625 for the report data corresponding to a received DICOM image by utilizing a common identifier extracted from the DICOM image.

In some embodiments, the report data can correspond to a plurality of DICOM images. For example, the report data can include natural language text describing a plurality of medical scans of a patient that can include multiple sequences, multiple modalities, and/or multiple medical scans taken over time. In such embodiments, the patient identifying text and/or annotation data detected in the report data can also be applied to de-identify and/or generate annotation data for the plurality of DICOM images it describes. In such embodiments, the medical picture archive integration system 2600 can query the medical picture archive system 2620 for one or more additional DICOM images corresponding to the report data, and de-identified data and annotation data for these additional DICOM images can be generated accordingly by utilizing the report data.

In some embodiments, as shown in FIG. 8E, the medical picture archive system 2620 communicates with the report database 2625. The medical picture archive system 2620 can request the report data corresponding to the DICOM image from the report database 2625, and can transmit the report data to the medical picture archive integration system 2600 via a DICOM communication protocol for receipt via receiver 2602. The medical picture archive system 2620 can query the report database 2625 for the report data, utilizing a common identifier extracted from the corresponding DICOM image, in response to determining to send the corresponding DICOM image to the medical picture archive integration system 2600.

FIG. 8F presents an embodiment where report data is generated by the annotating system 2612 and is transmitted, via a transmitter 2605, to the report database 2625, for example via a DICOM communication protocol or other protocol recognized by the report database 2625. In other embodiments, the report data is instead transmitted via transmitter 2604 to the medical picture archive system 2620, and the medical picture archive system 2620 transmits the report data to the report database 2625.

The report data can be generated by the annotating system 2612 as output of performing the inference function on the de-identified medical scan. The report data can include natural language text data 448 generated automatically based on other diagnosis data 440 such as abnormality annotation data 442 determined by performing the inference function, for example, by utilizing a medical scan natural language generating function trained by the medical scan natural language analysis system 114. The report data can be generated instead of, or in addition to, the annotated DICOM file.

FIG. 9 presents a flowchart illustrating a method for execution by a medical picture archive integration system 2600 that includes a first memory and a second memory that store executable instructions that, when executed by at least one first processor and at least one second processor, respectfully, cause the medical picture archive integration system to perform the steps below. In various embodiments, the first memory and at least one first processor are implemented by utilizing, respectfully, the memory 2654 and processing system 2652 of FIG. 8B. In various embodiments, the second memory is implemented by utilizing the memory 2674 and/or the memory 2684 of FIG. 8B. In various embodiments, the at least one second processor is implemented by utilizing the processing system 2682 of FIG. 8B.

Step 2702 includes receiving, from a medical picture archive system via a receiver, a first DICOM image for storage in the first memory, designated for PHI, where the first DICOM image includes at least one patient identifier. Step 2704 includes performing, via at least one first processor coupled to the first memory and designated for PHI, a de-identification function on the first DICOM image to identify the at least one patient identifier and generate a first de-identified medical scan that does not include the at least one patient identifier.

Step 2706 includes storing the first de-identified medical scan in a second memory that is separate from the first memory. Step 2708 includes receiving, via a network interface communicating with a network that does not include the medical picture archive system, first model parameters from a central server.

Step 2710 includes retrieving the first de-identified medical scan from the second memory. Step 2712 includes utilizing the first model parameters to perform a first inference function on the first de-identified medical scan to generate first annotation data via at least one second processor that is different from the at least one first processor. Step 2714 includes generating, via the at least one second processor, a first annotated DICOM file for transmission to the medical picture archive system via a transmitter, where the first annotated DICOM file includes the first annotation data and further includes an identifier that indicates the first DICOM image. In various embodiments, the first annotated DICOM file is a DICOM presentation state file.

In various embodiments, the second memory further includes operational instructions that, when executed by the at least one second processor, further cause the medical picture archive integration system to retrieve a second de-identified medical scan from the de-identified image storage system, where the second de-identified medical scan was generated by the at least one first processor by performing the de-identification function on a second DICOM image received from the medical picture archive system. The updated model parameters are utilized to perform the first inference function on the second de-identified medical scan to generate second annotation data. A second annotated DICOM file is generated for transmission to the medical picture archive system via the transmitter, where the second annotated DICOM file includes the second annotation data and further includes an identifier that indicates the second DICOM image.

In various embodiments, the second memory stores a plurality of de-identified medical scans generated by the at least one first processor by performing the de-identification function on a corresponding plurality of DICOM images received from the medical picture archive system via the receiver. The plurality of de-identified medical scans is transmitted to the central server via the network interface, and the central server generates the first model parameters by performing a training function on training data that includes the plurality of de-identified medical scans.

In various embodiments, the central server generates the first model parameters by performing a training function on training data that includes a plurality of de-identified medical scans received from a plurality of medical picture archive integration systems via the network. Each of the plurality of medical picture archive integration systems communicates bidirectionally with a corresponding one of a plurality of medical picture archive systems, and the plurality of de-identified medical scans corresponds to a plurality of DICOM images stored by the plurality of medical picture archive integration systems.

In various embodiments, the first de-identified medical scan indicates a scan category of the first DICOM image. The second memory further stores operational instructions that, when executed by the at least one second processor, further cause the medical picture archive integration system to select the first inference function from a set of inference functions based on the scan category. The set of inference functions corresponds to a set of unique scan categories that includes the scan category. In various embodiments, each unique scan category of the set of unique scan categories is characterized by one of a plurality of modalities and one of a plurality of anatomical regions.

In various embodiments, the first memory further stores operational instructions that, when executed by the at least one first processor, further cause the medical picture archive integration system to receive a plurality of DICOM image data from the medical picture archive system via the receiver for storage in the first memory in response to a query transmitted to the medical picture archive system via the transmitter. The query is generated by the medical picture archive integration system in response to a request indicating a new scan category received from the central server via the network. The new scan category is not included in the set of unique scan categories, and the plurality of DICOM image data corresponds to the new scan category. The de-identification function is performed on the plurality of DICOM image data to generate a plurality of de-identified medical scans for transmission to the central server via the network.

The second memory further stores operational instructions that, when executed by the at least one second processor, further cause the medical picture archive integration system to receive second model parameters from the central server via the network for a new inference function corresponding to the new scan category. The set of inference functions is updated to include the new inference function. The second de-identified medical scan is retrieved from the first memory, where the second de-identified medical scan was generated by the at least one first processor by performing the de-identification function on a second DICOM image received from the medical picture archive system. The new inference function is selected from the set of inference functions by determining the second de-identified medical scan indicates the second DICOM image corresponds to the new scan category. The second model parameters are utilized to perform the new inference function on the second de-identified medical scan to generate second annotation data. A second annotated DICOM file is generated for transmission to the medical picture archive system via the transmitter, where the second annotated DICOM file includes the second annotation data and further includes an identifier that indicates the second DICOM image.

In various embodiments, the medical picture archive integration system generates parameter data for transmission to the medical picture archive system that indicates the set of unique scan categories. The medical picture archive system automatically transmits the first DICOM image to the medical picture archive integration system in response to determining that the first DICOM image compares favorably to one of the set of unique scan categories.

In various embodiments, the second memory further stores operational instructions that, when executed by the at least one second processor, cause the medical picture archive integration system to generate a natural language report data is based on the first annotation data and to transmit, via a second transmitter, the natural language report data to a report database associated with the medical picture archive integration system, where the natural language report data includes an identifier corresponding to the first DICOM image.

In various embodiments, the first memory further stores operational instructions that, when executed by the at least one first processor, cause the medical picture archive integration system to receive, via a second receiver, a natural language report corresponding to the first DICOM image from the report database. A set of patient identifying text included in the natural language report are identified. Performing the de-identification function on the first DICOM image includes searching the first DICOM image for the set of patient identifying text to identify the at least one patient identifier.

In various embodiments, the first memory is managed by a medical entity associated with the medical picture archive system. The medical picture archive integration system is located at a first geographic site corresponding to the medical entity, and the central server is located at a second geographic site. In various embodiments, the first memory is decoupled from the network to prevent the first DICOM image that includes the at least one patient identifier from being communicated via the network. In various embodiments, the medical picture archive system is a Picture Archive and Communication System (PACS) server, and the first DICOM image is received in response to a query sent to the medical picture archive system by the transmitter in accordance with a DICOM communication protocol.

FIG. 10A presents an embodiment of a de-identification system 2800. The de-identification system 2800 can be utilized to implement the de-identification system 2608 of FIGS. 8A-8F. In some embodiments, the de-identification system 2800 can be utilized by other subsystems to de-identify image data, medical report data, private fields of medical scan entries 352 such as patient identifier data 431, and/or other private fields stored in databases of the database memory device 340.

The de-identification system can be operable to receive, from at least one first entity, a medical scan and a medical report corresponding to the medical scan. A set of patient identifiers can be identified in a subset of fields of a header of the medical scan. A header anonymization function can be performed on each of the set of patient identifiers to generate a corresponding set of anonymized fields. A de-identified medical scan can be generated by replacing the subset of fields of the header of the medical scan with the corresponding set of anonymized fields.

A subset of patient identifiers of the set of patient identifiers can be identified in the medical report by searching text of the medical report for the set of patient identifiers. A text anonymization function can be performed on the subset of patient identifiers to generate corresponding anonymized placeholder text for each of the subset of patient identifiers. A de-identified medical report can be generated by replacing each of the subset of patient identifiers with the corresponding anonymized placeholder text. The de-identified medical scan and the de-identified medical report can be transmitted to a second entity via a network.

As shown in FIG. 10A, the de-identification system 2800 can include at least one receiver 2802 operable to receive medical scans, such as medical scans in a DICOM image format. The at least one receiver 2802 is further operable to receive medical reports, such as report data 449 or other reports containing natural language text diagnosing, describing, or otherwise associated the medical scans received by the de-identification system. The medical scans and report data can be received from the same or different entity, and can be received by the same or different receiver 2802 in accordance with the same or different communication protocol. For example, the medical scans can be received from the medical picture archive system 2620 of FIGS. 8A-8F and the report data can be received from the report database 2625 of FIGS. 8D-8F. In such embodiments, the receiver 2802 can be utilized to implement the receiver 2602 of FIG. 8B.

The de-identification system 2800 can further include a processing system 2804 that includes at least one processor, and a memory 2806. The memory 2806 can store operational instructions that, when executed by the processing system, cause the de-identification system to perform at least one patient identifier detection function on the received medical scan and/or the medical report to identify a set of patient identifiers in the medical scan and/or the medical report. The operational instructions, when executed by the processing system, can further cause the de-identification system to perform an anonymization function on the medical scan and/or the medical report to generate a de-identified medical scan and/or a de-identified medical report that do not include the set of patient identifiers found in performing the at least one patient identifier detection function. Generating the de-identified medical scan can include generating a de-identified header and generating de-identified image data, where the de-identified medical scan includes both the de-identified header and the de-identified image data. The memory 2806 can be isolated from Internet connectivity, and can be designated for PHI.

The de-identification system 2800 can further include at least one transmitter 2808, operable to transmit the de-identified medical scan and de-identified medical report. The de-identified medical scan and de-identified medical report can be transmitted back to the same entity from which they were received, respectively, and/or can be transmitted to a separate entity. For example, the at least one transmitter can transmit the de-identified medical scan to the de-identified image storage system 2610 of FIGS. 8A-8F and/or can transmit the de-identified medical scan to central server system 2640 via network 2630 of FIGS. 8A-8F. In such embodiments, the transmitter 2808 can be utilized to implement the interface 2655 of FIG. 8B. The receiver 2802, processing system 2804, memory 2806, and/or transmitter 2808 can be connected via bus 2810.

Some or all of the at least one patient identifier detection function and/or at least one anonymization function as discussed herein can be trained and/or implemented by one or subsystems 101 in the same fashion as other medical scan analysis functions discussed herein, can be stored in medical scan analysis function database 346 of FIG. 3, and/or can otherwise be characterized by some or all fields of a medical scan analysis function entry 356 of FIG. 5.

The de-identification system 2800 can perform separate patient identifier detection functions on the header of a medical report and/or medical scan, on the text data of the medical report, and/or on the image data of the medical scan, such as text extracted from the image data of the medical scan. Performance of each of these functions generates an output of its own set of identified patient identifiers. Combining these sets of patient identifiers yields a blacklist term set. A second pass of the header of a medical report and/or medical scan, on the text data of the medical report, and/or on the image data of the medical scan that utilizes this blacklist term set can catch any terms that were missed by the respective patient identifier detection function, and thus, the outputs of these multiple identification processes can support each other. For example, some of the data in the headers will be in a structured form and can thus be easier to reliably identify. This can be exploited and used to further anonymize these identifiers when they appear in free text header fields, report data, and/or in the image data of the medical scan. Meanwhile, unstructured text in free text header fields, report data, and/or image data of the medical scan likely includes pertinent clinical information to be preserved in the anonymization process, for example, so it can be leveraged by at least one subsystem 101 and/or so it can be leveraged in training at least one medical scan analysis function.

At least one first patient identifier detection function can include extracting the data in a subset of fields of a DICOM header, or another header or other metadata of the medical scan and/or medical report with a known type that corresponds to patient identifying data. For example, this patient identifying subset of fields can include a name field, a patient ID number field or other unique patient identifier field, a date field, a time field, an age field, an accession number field, SOP instance UID, and/or other fields that could be utilized to identify the patient and/or contain private information. A non-identifying subset of fields of the header can include hospital identifiers, machine model identifiers, and/or some or all fields of medical scan entry 352 that do not correspond to patient identifying data. The patient identifying subset of fields and the non-identifying subset of fields can be mutually exclusive and collectively exhaustive with respect to the header. The at least one patient identifier function can include generating a first set of patient identifiers by ignoring the non-identifying subset of fields and extracting the entries of the patient identifying subset of fields only. This first set of patient identifiers can be anonymized to generate a de-identified header as discussed herein.

In some embodiments, at least one second patient identifier detection function can be performed on the report data of the medical report. The at least one second patient identifier detection function can include identifying patient identifying text in the report data by performing a natural language analysis function, for example, trained by the medical scan natural language analysis system 114. For example, the at least one second patient identifier detection function can leverage the known structure of the medical report and/or context of the medical report. A second set of patient identifiers corresponding to the patient identifying text can be determined, and the second set of patient identifiers can be anonymized to generate a de-identified medical report. In some embodiments, a de-identified medical report includes clinical information, for example, because the portion of the original medical report that includes the clinical information was deemed to be free of patient identifying text and/or because the portion of the original medical report that includes the clinical information was determined to include pertinent information to be preserved.

In some embodiments, the medical report includes image data corresponding to freehand or typed text. For example the medical report can correspond to a digitized scan of original freehand text written by a radiologist or other medical professional. In such embodiments, the patient identifier detection function can first extract the text from the freehand text in the image data to generate text data before the at least one second patient identifier detection function is performed on the text of the medical report to generate the second set of patient identifiers.

In some embodiments, the at least one second patient identifier detection function can similarly be utilized to identify patient identifying text in free text fields and/or unstructured text fields of a DICOM header and/or other metadata of the medical scan and/or medical report data by performing a natural language analysis function, for example, trained by the medical scan natural language analysis system 114. A third set of patient identifiers corresponding to this patient identifying text of the free text and/or unstructured header fields can be determined, and the third set of patient identifiers can be anonymized to generate de-identified free text header field and/or unstructured header fields. In some embodiments, a de-identified free text header field and/or unstructured header field includes clinical information, for example, because the portion of the original corresponding header field that includes the clinical information was deemed to be free of patient identifying text and/or because the portion of the original corresponding header field that includes the clinical information was determined to include pertinent information to be preserved.

Patient identifiers can also be included in the image data of the medical scan itself. For example, freehand text corresponding to a patient name written on a hard copy of the medical scan before digitizing can be included in the image data, as discussed in conjunction with FIG. 10B. Other patient identifiers, such as information included on a patient wristband or other identifying information located on or within the vicinity of the patient may have been captured when the medical scan was taken, and can thus be included in the image. At least one third patient identifier detection function can include extracting text from the image data and/or detecting non-text identifiers in the image data by performing a medical scan image analysis function, for example, trained by the medical scan image analysis system 112. For example, detected text that corresponds to an image location known to include patient identifiers, detected text that corresponds to a format of a patient identifier, and/or or detected text or other image data determined to correspond to a patient identifier can be identified. The at least one third patient identifier detection function can further include identifying patient identifying text in the text extracted from the image data by performing the at least one second patient identifier detection function and/or by performing a natural language analysis function. A fourth set of patient identifiers corresponding to patient identifying text or other patient identifiers detected in the image data of the medical scan can be determined, and the fourth set of patient identifiers can be anonymized in the image data to generate de-identified image data of the medical scan as described herein. In particular, the fourth set of patient identifiers can be detected in a set of regions of image data of the medical scan, and the set of regions of the image data can be anonymized.

In some embodiments, only a subset of the patient identifier detection functions described herein are performed to generate respective sets of patient identifiers for anonymization. In some embodiments, additional patient identifier detection functions can be performed on the medical scan and/or medical report to determine additional respective sets of patient identifiers for anonymization. The sets of patient identifiers outputted by performing each patient identifier detection function can have a null or non-null intersection. The sets of patient identifiers outputted by performing each patient identifier function can have null or non-null set differences.

Cases where the sets of patient identifiers have non-null set differences can indicate that a patient identifier detected by one function may have been missed by another function. The combined set of patient identifiers, for example, generated as the union of the sets of sets of patient identifiers outputted by performing each patient identifier function, can be used to build a blacklist term set, for example, stored in memory 2806. The blacklist term set can designate the final set of terms to be anonymized. A second pass of header data, medical scans, medical reports, and/or any free text extracted from the header data, the medical scan, and/or the medical report can be performed by utilizing the blacklist term set to flag terms for anonymization that were not caught in performing the respective at least one patient identifier detection function. For example, performing the second pass can include identifying at least one patient identifier of the blacklist term set in the header, medical report, and/or image data of the medical scan. This can include by searching corresponding extracted text of the header, medical report, and/or image data for terms included in blacklist term set and/or by determining if each term in the extracted text is included in the blacklist term set.

In some embodiments, at least one patient identifier is not detected until the second pass is performed. Consider an example where a free text field of a DICOM header included a patient name that was not detected in performing a respective patient identifier detection function on the free text field of the DICOM header. However, the patient name was successfully identified in the text of the medical report in performing a patient identifier detection function on the medical report. This patient name is added to the blacklist term list, and is detected in a second pass of the free text field of the DICOM header. In response to detection in the second pass, the patient name of the free text field of the DICOM header can be anonymized accordingly to generate a de-identified free text field. Consider a further example where the patient name is included in the image data of the medical scan, but was not detected in performing a respective patient identifier detection function on the free text field of the DICOM header. In the second pass, this patient name can be detected in at least one region of image data of the medical scan by searching the image data for the blacklist term set.

In some embodiments, performing some or all of the patient identifier detection functions includes identifying a set of non-identifying terms, such as the non-identifying subset of fields of the header. In particular, the non-identifying terms can include terms identified as clinical information and/or other terms determined to be preserved. The combined set of non-identifying terms, for example, generated as the union of the sets of sets of non-identifying outputted by performing each patient identifier function, can be used to build a whitelist term set, for example, stored in memory 2806. Performing the second pass can further include identifying at least one non-identifying term of the whitelist term set in the header, medical report, and/or image data of the medical scan, and determining not to anonymize, or to otherwise ignore, the non-identifying term.

In various embodiments, some or all terms of the whitelist term set can be removed from the blacklist term set. In particular, at least one term previously identified as a patient identifier in performing one or more patient identifier detection functions is determined to be ignored and not anonymized in response to determining the term is included in the whitelist term set. This can help ensure that clinically important information is not anonymized, and is thus preserved in the de-identified medical scan and de-identified medical report.

In some embodiments, the second pass can be performed after each of the patient identifier detection functions are performed. For example, performing the anonymization function can include performing this second pass by utilizing the blacklist term set to determine the final set of terms to be anonymized. New portions of text in header fields, not previously detected in generating the first set of patient identifiers or the third set of patient identifiers, can be flagged for anonymization by determining these new portions of text correspond to terms of the blacklist term set. New portions of text the medical report, not previously detected in generating in the second set of patient identifiers, can be flagged for anonymization by determining these new portions of text correspond to terms of the blacklist term set. New regions of the image data of the medical scan, not previously detected in generating the fourth set of patient identifiers, can be flagged for anonymization by determining these new portions of text correspond to terms of the blacklist term set.

In some embodiments, the blacklist term set is built as each patient identifier detection function is performed, and performance of subsequent patient identifier detection functions includes utilizing the current blacklist term set. For example, performing the second patient identifier detection function can include identifying a first subset of the blacklist term set in the medical report by searching the text of the medical report for the blacklist term set and/or by determining if each term in the text of the medical report is included in the blacklist term set. Performing the second patient identifier detection function can further include identifying at least one term in the medical report that is included in the whitelist term set, and determining to ignore the term in response. The first subset can be anonymized to generate the de-identified medical report as discussed herein. New patient identifiers not already found can be appended to the blacklist term set, and the updated blacklist term set can be applied to perform a second search of the header and/or image data of the medical scan, and at least one of the new patient identifiers can be identified in the header in the second search of the header and/or in the image data in a second search of the image data. These newly identified patient identifiers in the header and/or image data are anonymized in generating the de-identified medical scan.

As another example, a second subset of the blacklist term set can be detected in a set of regions of image data of the medical scan by performing the medical scan image analysis function on image data of the medical scan, where the image analysis function includes searching the image data for the set of patient identifiers. For example, the medical scan image analysis function can include searching the image data for text, and the second subset can include detected text that matches one or more terms of the blacklist term set. In some embodiments, detected text that matches one or more terms of the whitelist term set can be ignored. The second subset can be anonymized to generate de-identified image data as discussed herein. New patient identifiers that are detected can be appended to the blacklist term set, and the updated blacklist term set can be applied to perform a second search of the header and/or metadata of the medical scan, and/or can be applied to perform a second search of the medical report. At least one of the new patient identifiers can be identified in the header as a result of performing the second search of the header and/or at least one of the new patient identifiers can be identified medical report as a result of performing the second search of the medical report. These newly identified patient identifiers can be anonymized in the header along with the originally identified blacklist term set in generating the de-identified header, and/or can be anonymized in the medical report along with the originally identified first subset in generating the de-identified medical report.

In some embodiments, the memory 2806 further stores a global blacklist, for example, that includes a vast set of known patient identifying terms. In some embodiments, the global blacklist is also utilized by at least one patient identifier detection function and/or in performing the second pass to determine patient identifying terms for anonymization. In some embodiments, the blacklist term set generated for a particular medical scan and corresponding medical report can be appended to the global blacklist for use in performing the second pass and/or in detecting patient identifiers in subsequently received medical scans and/or medical reports.

Alternatively or in addition, the memory 2806 can further store a global whitelist, for example, that includes a vast set of terms that can be ignored. In particular, the global whitelist can include clinical terms and/or other terms that are deemed beneficial to preserve that do not correspond to patient identifying information. In some embodiments, the global whitelist is utilized by at least one patient identifier detection function and/or in performing the second pass to determine terms to ignore in the header, image data, and/or medical report. In some embodiments, the whitelist term set generated for a particular medical scan and corresponding medical report can be appended to the global whitelist for use in performing the second pass and/or in ignoring terms in subsequently received medical scans and/or medical reports.

Alternatively or in addition, the memory 2806 can further store a global graylist, for example, that includes ambiguous terms that could be patient identifying terms in some contexts, but non-identifying terms in other contexts. For example, “Parkinson” could correspond to patient identifying data if part of a patient name such as “John Parkinson”, but could correspond to non-patient identifying data meant to be ignored and preserved in the de-identified medical report and/or de-identified medical scan if part of a diagnosis term such as “Parkinson's disease.” In some embodiments, the global graylist is also utilized in performing the second pass and/or in performing at least one patient identifier detection function to determine that a term is included in the graylist, and to further determine whether the term should be added to the blacklist term set for anonymization or whitelist term set to be ignored by leveraging context of accompanying text, by leveraging known data types of a header field from which the term was extracted, by leveraging known structure of the term, by leveraging known data types of a location of the image data from which the term was extracted, and/or by leveraging other contextual information. In some embodiments, the graylist term set can be updated based on blacklist and/or whitelist term sets for a particular medical scan and corresponding medical report.

In some embodiments, the at least one anonymization function includes a fiducial replacement function. For example, some or all of the blacklist term set can be replaced with a corresponding, global fiducial in the header, report data, and/or image data. In some embodiments, the global fiducial can be selected from a set of global fiducials based on a type of the corresponding patient identifier. Each patient identifier detected in the header and/or medical report can be replaced with a corresponding one of the set of global text fiducials. Each patient identifiers detected in the image data can be replaced with a corresponding one of the set of global image fiducials. For example, one or more global image fiducials can overlay pixels of regions of the image data that include the identifying patient data, to obfuscate the identifying patient data in the de-identified image data.

The global text fiducials and/or global image fiducials can be recognizable by inference functions and/or training functions, for example, where the global text fiducials and global image fiducials are ignored when processed in a training step to train an inference function and/or are ignored in an inference step when processed by an inference function. Furthermore, the global text fiducials and/or global image fiducials can be recognizable by a human viewing the header, medical report, and/or image data. For example, a radiologist or other medical professional, upon viewing a header, medical report, and/or image data, can clearly identify the location of a patient identifier that was replaced by the fiducial and/or can identify the type of patient identifier that was replaced by the fiducial.

As an example, the name “John Smith” can be replaced in a header and/or medical report with the text “%PATIENT NAME%”, where the text “%PATIENT NAME%” is a global fiducial for name types of the header and/or the text of medical reports. The training step and/or inference step of medical scan natural language analysis functions can recognize and ignore text that matches “%PATIENT NAME%” automatically.

FIG. 10B illustrates an example of anonymizing patient identifiers in image data of a medical scan. In this example, the name “John Smith” and the date “May 4, 2010” is detected as freehand text in the original image data of a medical scan. The regions of the image data that include the patient identifiers can each be replaced by global fiducial in the shape of a rectangular bar, or any other shape. As shown in FIG. 10B, a first region corresponding to the location of “John Smith” in the original image data is replaced by fiducial 2820 in the de-identified image data, and a second region corresponding to the location of “May, 4, 2010” in the original image data is replaced by fiducial 2822 in the de-identified image data. The size, shape, and/or location of each global visual fiducial can be automatically determined based on the size, shape, and/or location of the region that includes the patient identifier to minimize the amount of the image data that is obfuscated, while still ensuring the entirety of the text is covered. While not depicted in FIG. 10B, the fiducial can be of a particular color, for example, where pixels of the particular color are automatically recognized by the training step and/or inference step of medical scan image analysis functions to indicate that the corresponding region be ignored, and/or where the particular color is not included in the original medical scan and/or is known to not be included in any medical scans. The fiducial can include text recognizable to human inspection such as “%PATIENT NAME” and “%DATE” as depicted in FIG. 10B, and/or can include a QR code, logo, or other unique symbol recognizable to human inspection and/or automatically recognizable by the training step and/or inference step of medical scan image analysis functions to indicate that the corresponding region be ignored.

In some embodiments, other anonymization functions can be performed on different ones of the patient identifying subset of fields to generate the de-identified header, de-identified report data, and/or de-identified image data. For example, based on the type of identifying data of each field of the header, different types of header anonymization functions and/or text anonymization functions can be selected and utilized on the header fields, text of the report, and/or text extracted from the image data. A set of anonymization functions can include a shift function, for example, utilized to offset a date, time or other temporal data by a determined amount to preserve absolute time difference and/or to preserve relative order over multiple medical scans and/or medical reports of a single patient. FIG. 10B depicts an example where the shift function is performed on the date detected in the image data to generate fiducial 2822, where the determined amount is 10 years and 1 month. The determined amount can be determined by the de-identification system randomly and/or pseudo-randomly for each patient and/or for each medical scan and corresponding medical report, ensuring the original date cannot be recovered by utilizing a known offset. In various embodiments, other medical scans and/or medical reports are fetched for the same patient by utilizing a patient ID number or other unique patient identifier of the header. These medial scans and reports can be anonymized as well, where the dates and/or times detected in these medical scans and/or medical reports offset by the same determined amount, randomized or pseudo-randomized for particular patient ID number, for example, based on performing a hash function on the patient ID number.

The set of anonymization functions can include at least one hash function, for example utilized to hash a unique patient ID such as a patient ID number, accession number, and/or SOP instance UID of the header and/or text. In some embodiments, the hashed SOP instance UID, accession number, and/or patient ID number are prepended with a unique identifier, stored in a database of the memory 2806 and/or shared with the entities to which the de-identified medical scans and/or medical reports are transmitted, so that de-identified medical scans and their corresponding de-identified medical reports can be linked and retrieved retroactively. Similarly, longitudinal data can be preserved as multiple medical scans and/or medical reports of the same patient will be assigned the same hashed patient ID.

The set of anonymization functions can further include at least one manipulator function for some types of patient identifiers. Some values of header fields and/or report text that would normally not be considered private information can be considered identifying patient data if they correspond to an outlier value or other rare value that could then be utilized to identify the corresponding patient from a very small subset of possible options. For example, a patient age over 89 could be utilized to determine the identity of the patient, for example, if there are very few patients over the age of 89. To prevent such cases, in response to determining that a patient identifier corresponds to an outlier value and/or in response to determining that a patient identifier compares unfavorably to a normal-range threshold value, the patient identifier can be capped at the normal-range threshold value or can otherwise be manipulated. For example, a normal-range threshold value corresponding to age can be set at 89, and generating a de-identified patient age can include capping patient ages that are higher than 89 at 89 and/or can include keeping the same value for patient ages that are less than or equal to 89.

In some embodiments, the de-identified header data is utilized to replace the corresponding first subset of patient identifiers detected in the medical report with text of the de-identified header fields. In other embodiments, a set of text anonymization functions includes a global text fiducial replacement function, shift function, a hash function, and/or manipulator functions that anonymize the corresponding types of patient identifiers in the medical report separately.

In some embodiments where the image data of a medical scan includes an anatomical region corresponding to a patient's head, the image data may include an identifying facial structure and/or facial features that could be utilized to determine the patient's identity. For example, a database of facial images, mapped to a corresponding plurality of people including the patient, could be searched and a facial recognition function could be utilized to identify the patient in the database. Thus, facial structure included in the image data can be considered patient identifying data.

To prevent this problem and maintain patient privacy, the de-identification system can further be implemented to perform facial obfuscation for facial structure detected in medical scans. At least one region of the image data that includes identifying facial structure can be determined by utilizing a medical image analysis function. For example, the medical image analysis function can include a facial detection function that determines the regions of the image data that include identifying facial structure based on searching the image data for pixels with a density value that corresponds to facial skin, facial bone structure, or other density of an anatomical mass type that corresponds to identifying facial structure, and the facial obfuscation function can be performed on the identified pixels. Alternatively or in addition, the facial detection function can determine the region based on identifying at least one shape in the image data that corresponds to a facial structure.

The image obfuscation function can include a facial structure obfuscation function performed on the medical scan to generate de-identified image data that does not include identifying facial structure. For example, the facial structure obfuscation function can mask, scramble, replace with a fiducial, or otherwise obfuscate the pixels of the region identified by the facial detection function. In some embodiments, the facial structure obfuscation function can perform a one-way function on the region that preserves abnormalities of the corresponding portions of the image, such as nose fractures or facial skin legions, while still obfuscating the identifying facial structure such that the patient is not identifiable. For example, the pixels of the identifying facial structure can be altered such that they converge towards a fixed, generic facial structure. In some embodiments, a plurality of facial structure image data of a plurality of patients can be utilized to generate the generic facial structure, for example, corresponding to an average or other combination of the plurality of faces. For example, the pixels of the generic facial structure can be averaged with, superimposed upon, or otherwise combined with the pixels of the region of the image data identified by the facial detection function in generating the de-identified image data.

In some embodiments, a hash function can be performed on an average of the generic facial structure and the identified facial structure of the image data so that the generic facial structure cannot be utilized in conjunction with the resulting data of the de-identified image data to reproduce the original, identifying facial structure. In such embodiments, the hash function can alter the pixel values while still preserving abnormalities. In some embodiments, a plurality of random, generic facial structures can be generated by utilizing the plurality of facial structure image data, for example, where each if the plurality of facial structure image data are assigned a random or pseudo-random weight in an averaging function utilized to create the generic facial structure, where a new, random or pseudo-random set of weights are generated each time the facial structure obfuscation function is utilized to create a new, generic facial structure to be averaged with the identified facial structure in creating the de-identified image data to ensure the original identifying facial structure cannot be extracted from the resulting de-identified image data.

While facial obfuscation is described herein, similar techniques can be applied in a similar fashion to other anatomical regions that are determined to include patient identifiers and/or to other anatomical regions that can be utilized to extract patient identifying information if not anonymized.

In some embodiments, the at least one receiver 2802 is included in at least one transceiver, for example, enabling bidirectional communication between the medical picture archive system 2620 and/or the report database 2625. In such embodiments, the de-identification system 2800 can generate queries to the medical picture archive system 2620 and/or the report database 2625 for particular medical scans and/or medical reports, respectively. In particular, if the medical scan and medical report are stored and/or managed by separate memories and/or separate entities, they may not be received at the same time. However, a linking identifier, such as DICOM identifiers in headers or metadata of the medical scan and/or medical report, such accession number, patient ID number, SOP instance UID, or other linking identifier that maps the medical scan to the medical report can be utilized to fetch a medical report corresponding to a received medical scan and/or to fetch a medical scan corresponding to a received medical report via a query sent utilizing the at least one transceiver. For example, in response to receiving the medical scan from the medical picture archive system 2620, the de-identification system can extract a linking identifier from a DICOM header of the medical scan, and can query the report database 2625 for the corresponding medical report by indicating the linking identifier in the query. Conversely, in response to receiving the medical report from the report database 2625, the de-identification system can extract the linking identifier from a header, metadata, and/or text body of the medical report, and can query the medical picture archive system 2620 for the corresponding medical scan by indicating the linking identifier in the query. In some embodiments, a mapping of de-identified medical scans to original medical scans, and/or a mapping of de-identified medical reports to original medical reports can be stored in memory 2806. In some embodiments, linking identifiers such as patient ID numbers can be utilized to fetch additional medical scans, additional medical reports, or other longitudinal data corresponding to the same patient.

FIG. 11 presents a flowchart illustrating a method for execution by a de-identification system 2800 that stores executable instructions that, when executed by at least one processor, cause the de-identification to perform the steps below.

Step 2902 includes receiving from a first entity, via a receiver, a first medical scan and a medical report corresponding to the medical scan. Step 2904 includes identifying a set of patient identifiers in a subset of fields of a first header of the first medical scan. Step 2906 includes performing a header anonymization function on each of the set of patient identifiers to generate a corresponding set of anonymized fields. Step 2908 includes generating a first de-identified medical scan by replacing the subset of fields of the first header of the first medical scan with the corresponding set of anonymized fields. Step 2910 includes identifying a first subset of patient identifiers of the set of patient identifiers in the medical report by searching text of the medical report for the set of patient identifiers. Step 2912 includes performing a text anonymization function on the first subset of patient identifiers to generate corresponding anonymized placeholder text for each of the first subset of patient identifiers. Step 2914 includes generating a de-identified medical report by replacing each of the first subset of patient identifiers with the corresponding anonymized placeholder text. Step 2916 includes transmitting, via a transmitter, the de-identified first medical scan and the de-identified medical report to a second entity via a network.

In various embodiments, the medical scan is received from a Picture Archive and Communication System (PACS), where the medical report is received from a Radiology Information System (RIS), and where the first de-identified medical scan and the de-identified medical report are transmitted to a central server that is not affiliated with the PACS or the RIS. In various embodiments, first medical scan and the medical report are stored in a first memory for processing. The first memory is decoupled from the network to prevent the set of patient identifiers from being communicated via the network. The first de-identified medical scan and the de-identified medical report are stored in a second memory that is separate from the first memory. The first de-identified medical scan and the de-identified medical report are fetched from the second memory for transmission to the second entity.

In various embodiments, the header anonymization function performed on each of the set of patient identifiers is selected from a plurality of header anonymization functions based on one of a plurality of identifier types of the corresponding one of the subset of fields. In various embodiments, the plurality of identifier types includes a date type. A shift function corresponding to the date type is performed on a first date of the first header to generate the first de-identified medical scan, where the shift function includes offsetting the first date by a determined amount. A second medical scan is received, via the receiver, that includes a second header. A unique patient ID of the first header matches a unique patient ID of the second header. The shift function is performed on a second date of the second header by offsetting the second date by the determined amount to generate a second de-identified medical scan. The second de-identified medical scan is transmitted to the second entity via the network.

In various embodiments, the plurality of identifier types includes a unique patient ID type. A hash function corresponding the unique patient ID type is performed on the unique patient ID of the first header to generate the first de-identified medical scan. The hash function is performed on the unique patient ID of the second header to generate the second de-identified medical scan. An anonymized unique patient ID field of the first de-identified medical scan matches an anonymized unique patient ID field of the second de-identified medical scan as a result of the unique patient ID of the first header matching the unique patient ID of the second header.

In various embodiments, the plurality of identifier types includes a linking identifier type that maps the medical scan to the medical report. A hash function corresponding to the linking identifier type is performed on a linking identifier of the first header to generate a hashed linking identifier. A linking identifier field of the first de-identified medical scan includes the hashed linking identifier. Performing the text anonymization function on the first subset of patient identifiers includes determining one of the first subset of patient identifiers corresponds to linking identifier text and performing the hash function on the one of the first subset of patient identifiers to generate the hashed linking identifier, where the de-identified medical report includes the hashed linking identifier.

In various embodiments, a second subset of patient identifiers of the set of patient identifiers is identified in a set of regions of image data of the medical scan by performing an image analysis function on image data of the medical scan. The image analysis function includes searching the image data for the set of patient identifiers. An identifier type is determined for each of the second subset of patient identifiers. One of a plurality of image fiducials is selected for each of the second subset of patient identifiers based on the identifier type. De-identified image data is generated, where a set of regions of the de-identified image data, corresponding to the set of regions of the image data, includes the one of the plurality of image fiducials to obfuscate each of the second subset of patient identifiers. Generating the first de-identified medical scan further includes replacing the image data of the medical scan with the de-identified image data.

In various embodiments, a new patient identifier is identified in the medical report by performing a natural language analysis function on the medical report, where new patient identifier is not included in the set of patient identifiers. The set of patient identifiers is updated to include the new patient identifier prior to searching the image data of the medical scan for the set of patient identifiers, and the second subset of patient identifiers includes the new patient identifier.

In various embodiments, the memory further stores a global identifier blacklist. The natural language analysis function includes searching the medical report for a plurality of terms included in the global identifier blacklist to identify the new patient identifier. In various embodiments, the de-identification system determines that the global identifier blacklist does not include one of the set of patient identifiers, and the global identifier blacklist is updated to include the one of the set of patient identifiers.

In various embodiments, performing the image analysis function further includes identifying a new patient identifier in the image data, where new patient identifier is not included in the set of patient identifiers. Identifying text is extracted from a region of the image data corresponding to the new patient identifier. The new patient identifier is identified in the medical report by searching text of the medical report for the identifying text. The text anonymization function is performed on new patient identifier to generate anonymized placeholder text for the new patient identifier. Generating the de-identified medical report further includes replacing the identifying text with the anonymized placeholder text for the new patient identifier.

In various embodiments, generating the de-identified image data further includes detecting an identifying facial structure in the image data of the medical scan. Generating the de-identified image data includes performing a facial structure obfuscation function on the image data, and where the de-identified image data does not include the identifying facial structure.

In some embodiments, the medical scans discussed herein can include electrocardiogram (ECG) data indicating signal data for one or more leads corresponding to recorded electrical activity of the heart of a patient and/or other heart beat and/or heart rhythm information of a patient. This can include ECG data and/or EKG data. As used herein, ECG can interchangeably refer to EKG. Electrocardiogram data corresponding to data recorded by an ECG machine can be processed instead of or in addition to medical scans as discussed in the various embodiments of the medical scan processing system 100 discussed herein. For example, the same or different medical scan database 342 can includes ECG entries, as discussed in further detail in conjunction with FIG. 12B. One or more inference functions or other medical scan analysis functions discussed herein can utilize ECG signal data instead of or in addition to other medical scans as input and can generate diagnosis data as output.

FIG. 12A illustrates an ECG interpretation system 4002 that is operable to process captured images of ECG printouts to automatically generate diagnosis data. In particular, the ECG interpretation system 4002 is operable to receive captured images of ECG printouts, taken by an image capture devices 4012 such as a scanner or camera. An ECG printout can correspond to an ECG paper printout generated based on raw signal data recorded by a ECG machine. The ECG interpretation system 4002 enables a user of client device 120, such as a patient or a medical professional providing care for a patient, to receive automatically generated diagnosis data for an ECG printout. The user can send a captured image of the ECG printout to the ECG interpretation system 4002 via network 150. For example, as illustrated in FIG. 12A, the image capture device 4012 can be coupled to or can otherwise communicate with the client device 120. Alternatively, a captured image of an ECG printout can be uploaded to or can otherwise be received by the client device 120, for example, via the network 150, before transmission to the ECG interpretation system 4002. In some embodiments, the captured image corresponds to a digital ECG file that includes the raw signal data captured by the ECG machine, utilized by the ECG machine to generate a digital ECG file directly. The captured image can include any image data or signal data indicating at least one waveform generated by an ECG machine. As illustrated in FIG. 12A, multiple client devices 1-N corresponding to multiple users can transmit captured images to the ECG interpretation system 4002.

The ECG interpretation system can process a captured image by performing an ECG processing function 4005 to generate diagnosis data for the ECG printout. This can include reconstructing pseudo-raw signal data for multiple waveforms detected in the captured image, for example, corresponding to multiple ECG leads. The reconstructed pseudo-raw signal data can be utilized to generate diagnosis data by utilizing one or more neural network models and/or other machine learning models trained on ECG signal data as input label data and known ECG diagnosis data as output label data. The ECG processing function 4005 is discussed further in conjunction with FIGS. 12C-12E. Diagnosis data and/or the reconstructed pseudo-raw signal data generated can be transmitted to the corresponding client device for display via a user interface 4075. As illustrated in FIG. 12A, diagnosis data 1-N is generated for received captured images 1-N for transmission to the corresponding client devices 1-N from which the corresponding captured image was received. While not depicted in FIG. 12A, the diagnosis data and/or the reconstructed pseudo-raw signal data can be transmitted to the a client device 120 that is different from the client device that transmitted the captured image, where the different client device 120 corresponds to the same or different user.

Alternatively or in addition, the diagnosis data, reconstructed pseudo-raw signal data, and/or the captured image can also be transmitted to an ECG database 4342. The ECG database can be implemented by utilizing medical scan database 342, where the captured image data corresponds to image data 410 and/or where the diagnosis data corresponds to diagnosis data 440. The ECG database 4342 can be a different database of database storage system 140, and can communicate with some or all other subsystems 101. The ECG database 4342 can store a plurality of ECG entries, where some or all entries include captured images of ECG printouts generated by client devices 120 and/or diagnosis data generated by the ECG interpretation system 4002. Alternately or in addition, some or all ECG entries can correspond to other ECG printouts and/or raw signal data of other ECGs. These ECG entries can include diagnosis data generated by a medical professional. For example, such ECG entries can correspond to training data utilized by the ECG interpretation system 4002 or other system to train at least one inference function utilized in performing the ECG processing function 4005.

As shown in FIG. 12A, the ECG interpretation system 4002 can communicate bi-directionally, via network 150, with the ECG database 4342 and/or with other databases of the database storage system 140, with one or more client devices 120, and/or, while not shown in FIG. 12A, with one or more subsystems 101 of FIG. 1, with the central server system 2640, and/or with the medical picture archive system 2600.

In some embodiments, the ECG interpretation system 4002 is an additional subsystem 101 of the medical scan processing system 100, implemented by utilizing the subsystem memory device 245, subsystem processing device 235, and/or subsystem network interface 265 of FIG. 2A. For example, the ECG interpretation system 4002 can be implemented by utilizing the medical scan image analysis system 112 to train one or more computer vision models utilized to perform the ECG processing function 4005 and/or by utilizing the medical scan assisted review system 102 to present, via user interface 4075, diagnosis data in conjunction with the ECG printout in the captured image and/or in conjunction with a visualization of reconstructed pseudo-raw signal data. The ECG interpretation system 4002 can be implemented by utilizing any of the features discussed in conjunction with the captured image processing system of FIGS. 15A-15C.

In some embodiments, the ECG interpretation system 4002 utilizes, or otherwise communicates with, the central server system 2640. For example, the ECG database 4342 can be populated with de-identified data generated by the medical picture archive integration system 2600, for example, where the medical picture archive integration system 2600 is operable to generate de-identified ECGs from captured images of ECG printouts or from digitized ECG files. The ECG interpretation system 4002 can receive de-identified ECGs in training sets and/or for diagnosis with their diagnosis data and/or other relevant information directly from the medical picture archive integration system 2600, for example, where the diagnosis data is utilized to determine the medical labels for medical scans in the training set. As another example, the ECG interpretation system 4002 can perform one or more inference functions of the ECG processing function 4005 on de-identified ECGs that need to be diagnosed, received from the medical picture archive integration system 2600. The diagnosis data generated as output can be assigned to the medical scan in the medical picture archive integration system 2600. As another example, the ECG interpretation system 4002 can request de-identified ECGs and/or other corresponding information that match requested criteria for a training set utilized to train the ECG processing function 4005 and/or for new ECGs to be diagnosed. As another example, the ECG processing function 4005 can be utilized by the annotating system 2612 to generate diagnosis data for ECGs. In some embodiments, some or all of the ECG interpretation system 4002 is implemented by utilizing other subsystems 101 and/or is operable to perform functions or other operations described in conjunction with one or more other subsystems 101.

While FIG. 12A depicts communication between the client device and ECG interpretation system 4002 via network 150, in other embodiments, the client device can store application data for some or all of the ECG processing function 4005. For example, one or more client devices 120 of FIG. 12A can locally execute the application data to execute ECG processing function 4005 locally on captured images taken by or uploaded to the client device and to generate diagnosis data automatically in response.

FIG. 12B illustrates an example ECG entry 4452 of ECG database 4342. Alternatively or in addition, some or all fields of the ECG entry 4342 can correspond to data that can be transmitted in conjunction with captured image data of an ECG printout and/or diagnosis data, to represent data that can be generated in conjunction with generating diagnosis data for an ECG, and/or to represent data that can be utilized in conjunction with the captured image data of an ECG printout to generate the diagnosis data.

The ECG entry 4452 can include an ECG identifier 4453 that is unique to the entry and/or can be utilized to identify the ECG. The ECG identifier 4453 can correspond to the same or different type of identifier as medical scan entry identifier 353. The ECG entry 4452 can include ECH signal data 4410, which can include a plurality of voltage v. time coordinates 4415 characterizing the ECG signal of one of a plurality of ECG leads 4412. For example, the ECG signal data 4410 can include data characterizing waveforms for each of twelve ECG leads and/or a different number of ECG leads. Some or all of the signal data for some or all ECG leads 4412 can instead include other coordinate data, signal parameter data, waveform measurements such as some or all of measurement data 4443, and/or other graphical waveform data characterizing the corresponding signal. The ECG signal data 4410 can correspond to raw signal data, for example, captured directly by an ECG machine. Alternatively, the ECG signal data 4410 can correspond to reconstructed, pseudo-raw signal data, for example, generated by the ECG interpretation system 4002 from a captured image of an ECG printout.

The ECG entry can include ECG printout data 4416. The ECG printout data 4416 can include a captured image 4417, for example, corresponding to the captured image generated by client device 120 as discussed in conjunction with FIG. 12A. An ECG printout depicted in the captured image can correspond to a physical, paper printout of an ECG generated to reflect raw signal data recorded by a ECG machine. Alternatively or in addition, an ECG printout depicted in the captured image can instead correspond to a picture taken of an ECG monitor of an ECG machine, displaying raw signal data recorded by the ECG machine. Alternatively or in addition, an ECG printout depicted in the captured image can correspond to a picture taken of an ECG monitor of an ECG machine, displaying raw signal data recorded by the ECG machine. Alternatively or in addition, the ECG printout can correspond to a screenshot of a real-time display of raw signal data recorded by the ECG machine on an ECG monitor or other display device. The captured image can be stored in a JPEG, PNG, PDF, or other file format utilized to store image data. Alternatively or in addition, the ECG printout can correspond to a video of a real-time display of raw signal data recorded by the ECG machine on an ECG monitor or other display device, where the captured image corresponds to a video file.

The ECG printout data 4416 can include a receiving entity identifier 4418 indicating an identifier of the client device 120 from which the ECG printout was received by the ECG database 4342 and/or ECG interpretation system 4002, indicating an identifier of a user account from whom the ECG printout was sent to the ECG database 4342 and/or the ECG interpretation system 4002, and/or another identifier indicating an origin of the captured image. The ECG printout data 4416 can include additional details 4419 for the captured image, for example, included in the transmission of the captured image based on user input to user interface 4075 as discussed in FIGS. 13A-13C and/or automatically extracted by the ECG interpretation system 4002 from text or other information identified in the ECG printout. User account data associated with receiving entity identifier 4418 and/or the additional details 4419 can be utilized to determine some or all of the ECG classifier data 4420, patient history data 4430, diagnosis data 4440, diagnosis author data 4450, and/or display parameter data 4470.

The ECG entry can include ECG classifier data 4420, which can correspond to some or all of the medical scan classifier data 420. Some or all of the ECG scan classifier data can be determined based on additional details 4419 and/or determined based on a medical entity associated with client device 120. ECG classifier data 4420 can include originating entity data 4423, which can be the same or different from originating entity data 423, and/or can indicate a hospital or other medical entity from which the original ECG printout was generated. ECG classifier data 4420 can include geographic region data 4424 entity data 4423, which can be the same or different from geographic region data 424, and/or can indicate a geographic from which the original ECG printout was generated and/or from which a patient for whom the ECG corresponds to lives and/or is otherwise associated with. ECG classifier data 4420 can include machine data 4425, which can be the same or different from machine data 425, and/or can indicate the ECG machine model and/or ECG machine parameters corresponding to the ECG machine from which the original ECG printout was generated. ECG classifier data 4420 can include ECG date data 4426, which can be the same or different from scan date data 426, and/or can indicate a date, time, and/or other temporal data corresponding to when the ECG signals of the ECG printout were recorded. ECG classifier data 4420 can include ECG priority data 4427, which can be the same or different from scan priority data 427, and/or can indicate a priority value and/or queue value utilized to indicate a time-sensitivity for review and/or follow-up of the ECG, for example, based on the diagnosis data and/or based on the ECG date data. The ECG classifier data 4420 can include additional classifier data providing additional details regarding the ECG printout itself.

The ECG entry can include patient history data 4430, which can include patient identifier data 4431 identifying a patient of whom the ECG was recorded, which can be the same or different type of identifier as patient identifier 431. The patient history data 4430 can include risk factor data 4432 for the patient, which can same or different risk factors as risk factor data 432. Some or all of the risk factor data 4432 can include risk factors associated with cardiac-based diagnoses and/or risk factors that would aid in generating diagnosis data in conjunction with ECG data. The patient history data 4430 can include longitudinal data 4433, which can include one or more additional ECGs and/or one or more medical scans associated with the patient. The longitudinal quality score 4434 can be based on a quantity and/or time between some or all longitudinal data 4433 and/or can be based on the same or different factors as longitudinal quality score 434.

The ECG entry can include diagnosis data 4440. Some or all ECG entries can include diagnosis data 4440 generated by the ECG interpretation system 4002. Some or all ECG entries can include diagnosis data 4440 generated by human review of the ECG printout and/or by human review of raw signal data and/or pseudo-raw signal data of the ECG signal data 4410. The diagnosis data 4440 can include a binary abnormality identifier 4441 indicating whether or not the ECG is normal.

The diagnosis data 4440 can include measurement data 4443 indicating one or more measurements. The measurement data 4443 can include P wave data indicating time and/or voltage coordinate data of the P wave in the ECG signal data and/or corresponding measurements and/or characterization of the P wave. The measurement data 4443 can include QRS complex data indicating the Q wave, the R wave, and/or the S wave. The QRS complex data can include time and/or voltage coordinate data of the Q, R and/or S wave in the ECG signal data and/or can include corresponding measurements of the Q, R and/or S wave. The measurement data 4443 can include T wave data indicating time and/or voltage coordinate data of the T wave in the ECG signal data and/or corresponding measurements and/or characterization of the T wave. The measurement data 4443 can include a measurement for the PR interval, a measurement for the QRS duration, and/or a measurement for the QT interval. The measurement data 4443 can include a heart rate approximation. Some or all of the measurement data can be generated by the ECG interpretation system 4002 and/or can be extracted from text included in the ECG printout. The measurement data 4443 can further include additional binary abnormality identifiers indicating whether each of the measurements are normal or abnormal measurements, for example, based on whether or not the corresponding measurement falls within predefined threshold boundaries.

The diagnosis data can include abnormality data 4442 for one or more abnormalities, such as one or more abnormal rhythms. This can include data localizing detected abnormalities in the raw signal data and/or data characterizing one or more abnormalities, for example, based on measurement data 4443. The abnormality data 4442 can indicate the type of abnormality present in the ECG, and can indicate any abnormal type of rhythm or other abnormal features determined to be present in the ECG.

The diagnosis data 4440 can include one or more of medical codes 4447, which can include the same or different type of standardized medical codes as medical codes 4447, for example, based on the abnormality data 4442. The diagnosis data 4440 can include annotation data 4448, for example, utilized to provide text or visual indications of particular features in the ECG waveform that are normal or abnormal, for example for display via a user interface in conjunction with display of the ECG waveforms themselves to present some or all of the diagnosis data, for example, based on the abnormality data 4442. Some or all of the annotation data can indicate some or all of measurement data 4443. The annotation data 4448 can include some or all of the features of annotation data 448. The diagnosis data 4440 can include report data 4449, which can include natural language text describing the diagnosis and/or can include a formatted file that includes the captured image ECG printout and/or one or more reconstructed pseudo-raw signals for one or more leads. Report data 4449 can include some or all of the features of the report data 449.

The ECG entry can include diagnosis author data 4450, which can be the same or different from annotation author data 450. The diagnosis author data can indicate at least one diagnosis author identifier 4451, which can indicate function identifier in the medical scan analysis function database that generated some or all of the diagnosis data, such as an identifier of the ECG processing function 4005. Alternatively or in addition, the diagnosis author identifier 4451 can indicate a user identifier in the indicating a user that generated some or all of the diagnosis data, such as a user that generated additional diagnosis data as discussed in FIG. 12F and/or a user that generated diagnosis data for ECG entries utilized to train the ECG processing function 4005.

The ECG entry can include confidence score data 4460, which can be determined the same or different fashion as confidence score 460. The confidence score 460 can be determined as output of the ECG processing function 4005 in generating the diagnosis data, for example, indicating one or more probabilities that one or more features indicated in the diagnosis data is correct and/or indeed present and/or one indicating or more confidence intervals for one or more measurements or other features of the diagnosis data. The confidence score data can be further based on a determined quality of the captured image of the ECG printout, for example, based on resolution, brightness, or other factors that affect image quality. Diagnosis data generated for ECG printouts with lower image quality can be assigned lower confidence scores. The confidence score data can be further based on an accuracy of one or more functions utilized in performing the ECG processing function 4005. The confidence score data can be further based on whether or not human review of the automatically generated diagnosis data was provided, for example, where the confidence score data increases if human review confirms the automatically generated diagnosis data. The confidence score data can be assigned a higher and/or highest score when the diagnosis data was generated via human review and/or if the diagnosis data was utilized in one or more training sets utilized to train one or more inference functions.

The ECG entry can include display parameter data 4470, which can include interactive interface feature data 4471, which can include some or all of the interactive interface feature data 471 and/or can indicate interactive interface features utilized in displaying the diagnosis data and/or corresponding ECG signal data via user interface 4075 and/or indicating layout and/or formatting preference for generating a formatted report such as report data 4449. The display parameter data 4470 can indicate lead subset data 4472, indicating which leads that will have corresponding waveforms displayed via user interface 4075 and/or can indicate a layout and/or an ordering of waveforms for display via user interface 4075 based on their corresponding leads as lead ordering data 4473. The display parameter data 4470 can include waveform cropping data 4474 indicating whether and how one or more waveforms is cropped for display via user interface 4075. Some or all of the display parameter data 4470 can be based on a user profile and/or user account associated with a user that utilizes the ECG interpretation system 4002 and/or associated with a user that is associated with a corresponding client device utilized to display the user interface 4075 on a corresponding display device.

The ECG entry can include training set data 4490, which can indicate one or more training sets in which the ECG was utilized as training data, for example, to train one or more inference functions utilized by the ECG processing function 4005 and/or to train one or more functions with parameters stored in the medical scan analysis function database 346. This can include one or more training set identifier data 4491, which can be the same or different from training set identifier data 491.

FIGS. 12C-12E illustrate steps in performing the ECG processing function 4005. Some or all steps of the ECG processing function 4005 can utilize a same or different inference function that utilizes a computer vision model, a neural network, and/or or other machine learning model. Some or all of the functions illustrated in FIG. 12C can be trained by the ECG processing function 4005 or another subsystem 101 on training sets of captured images of ECG printouts, on raw signal data of ECGs, and/or other ECG waveform data. Some or all of the functions illustrated in FIG. 12C can utilize any of the fields of corresponding ECG entries 4452 for the set of training data as input labels and/or output labels to train the corresponding model. Some or all of the functions illustrated in FIG. 12C can have function parameters set by an administrator via interaction with a user interface. Some or all of the functions illustrated in FIG. 12C can have a corresponding entry in the medical scan analysis function database and/or can be trained and/or utilized by one or more other subsystems 101 as a medical scan analysis function as discussed herein.

As illustrated in FIG. 12C, a waveform detection function 4020 can be utilized to detect locations of waveforms in a captured image 4010, which can correspond to captured image 4417. The waveform detection function 4020 can utilize a computer vision model trained on a plurality of captured images of ECG printouts and/or trained on a plurality of captured images of single waveforms included in ECG printouts to detect waveforms in the captured image. The computer vision model can correspond to a neural network and/or a different machine learning model. The waveform detection function 4020 can utilize known layouts and/or formatting features of ECG printouts to detect the plurality of waveforms. The known layouts and/or formatting features of ECG printouts can further be utilized to detect the boundaries of the ECG printout itself in the captured image, for example, where other background outside the detected boundaries of the ECG printout itself are ignored and/or removed. Pre-processing can be performed to generate a grayscale image, to increase the contrast, to align a crooked image vertically, and/or to crop the ECG printout to a particular size, for example, based on detecting the gridlines, based on aligning the position and/or size of the gridlines to preset position and/or scale, and/or based on increasing contrast of the waveform and/or gridlines against other portions of the captured image.

The waveform detection function 4020 can utilize the uniform grid of a standard ECG printout and/or uniform relative layout of waveforms corresponding to each of the twelve leads to determine locations of the waveforms. Alternatively or in addition, the waveform detection function 4020 can detect labels for some or all of the twelve leads, such as “aVR” or “V1” in the captured image. Alternatively or in addition, the waveform detection function 4020 can detect known waveform shape features in the captured image, and can differentiate between waveforms of different leads based on known differences in the corresponding known waveform shape features. Alternatively or in addition, the waveform detection function 4020 can utilize uniform header formatting and/or text detection to locate header data located at the top of the ECG printout, and can determine the relative location of the waveforms based on their known relative position from the header. Detection of the header and/or known header formatting can be utilized to extract additional information, such as some or all of additional details 4419, from the header of the printout. This can include patient name, age, hospital information, and/or some or all of measurement data 4443 and/or initial diagnosis data utilized to generate diagnosis data.

Performance of the waveform detection function 4020 can result in waveform location data 1-K, where K is equal to twelve or a different number of waveforms in the image. This can, for example, indicate pixel coordinates for borders that include each waveforms, for example indicated in FIG. 12D as borders 4013. While FIG. 12D indicates that the extended waveform of lead II is not utilized, in some embodiments, the extended waveform of lead II is utilized instead of or in addition to the other waveform of lead II. While FIG. 12D depicts that the borders 4013 are generated for all twelve leads, one or more leads can be ignored for example if they are not included in the captured image, are determined to be obscured in the captured image, and/or if they are not utilized by further steps of the ECG processing function 4005 to generate diagnosis data.

The image partitioning function 4022 can then be utilized based on the waveform location data to generate waveform images 1-K. For example, as indicated in FIG. 12D, twelve waveform images 4014 can be generated by cropping the captured image in accordance with the borders 4013. The individual waveform images 1-K can be processed to generate pseudo-raw ECG signal data 1-K by performing signal reconstruction function 4024. This can include detecting the waveform in the waveform image, for example, in relation to detected gridlines of the ECG printout and/or by detecting darker pixels for the waveform and the gridlines against the lighter pixels background of the ECG printout. For example, pseudo-raw ECG signal data 4016, as illustrated in FIG. 12E, is generated as output to performing the signal reconstruction function 4024. This can include generating a discrete plurality of coordinate pairs, each indicating a time based on a determined x-value of a point on the waveform and a voltage based on a corresponding determined y-value of the point of the waveform based on the detected location of portions of the waveform in the waveform image relative to the gridlines. An origin x and/or y gridline can be automatically detected based on formatting features of the ECG printout and/or based on the location of the waveform relative to the plurality of gridlines and/or based on known relative boundaries of where the origin x and y gridlines should lie relative to features of the waveform.

As illustrated in FIG. 12E, signal reconstruction function 4024 can include a plurality of signal reconstruction functions specific to each of the twelve leads, where each of the plurality of signal reconstruction functions is performed on the corresponding one of the twelve waveform images to generate the corresponding pseudo-raw ECG signal data. Some or all of these signal reconstruction functions can be the same or different. Alternatively or in addition, performing the signal reconstruction function 4024 and/or performing one or more individual, lead-specific signal reconstruction functions can include generating some or all of the measurement data 4443 to characterize significant features determined in the waveform images.

The signal reconstruction function 4024 can utilize known time intervals and voltage intervals between gridlines along the vertical and horizontal axes to generate some or all of the measurement data. Some or all of the measurement data can be detected directly from the waveform image and/or from the pseudo-raw ECG signal data. Detecting the P, Q, R, S, and/or T wave can be based on utilizing a computer vision model trained on a training set of waveform images, a training set of raw ECG data, and/or a training set of pseudo-raw ECG signal data as input labels, and a corresponding plurality of P, Q, R, S, and/or T wave coordinate identifiers and/or measurements as output labels. For example, the output labels can indicate one or more coordinates of the ECG signal data that correspond to the corresponding wave, and/or can indicate one or more pixel coordinates of the waveform image that correspond to the corresponding wave. Signal reconstruction functions for different leads can be trained on separate training data corresponding to waveform images, a training set of raw ECG data, and/or a training set of pseudo-raw ECG signal data for the corresponding lead.

In some embodiments, the shape of the QRS complex and/or one or more individual waves are detected in the waveform image data to determine the location of the QRS complex and/or one or more individual waves in the waveform image data, for example, by utilizing a computer vision model trained to detect shapes of the QRS complex and/or one or more individual waves. In some embodiments, a smoothing function is applied to the pseudo-raw ECG signal data to remove extraneous noise and/or other minor waves that may be confused for the peaks of the P, Q, R, S, and/or T wave. In some embodiments, maximum amplitudes of the waveform image and/or pseudo-raw ECG signal data are determined to detect the peak of the corresponding wave. Once the waves are detected, corresponding interval measurements and heart rate measurements can be determined by utilizing the gridlines between wave locations and/or by utilizing corresponding time values of coordinates determined for the waves.

The pseudo-raw ECG signal data 1-K and/or some or all measurement data 4443 can be utilized as input to diagnosing function 4026. Alternatively or in addition, the waveform images themselves can be utilized as input to diagnosing function 4026, for example, where performance of the signal reconstruction function 4024 is skipped. The diagnosing function 4026 can utilize a plurality of diagnosing functions corresponding to each lead, for example, where each of twelve outputs of the signal reconstruction function 4024 are utilized as input to a corresponding one of twelve diagnosing functions. Each of the twelve diagnosing functions can utilize models trained on their own set of training data corresponding to waveform images, a training set of raw ECG data, and/or a training set of pseudo-raw ECG signal data for the corresponding lead. Diagnosis data can be determined for each lead separately, and a final diagnosis function can be utilized to consolidate the diagnosis data for each lead to determine the diagnosis data. Alternatively, all twelve leads can be fed into one model as input, where the model was trained on a training data corresponding to waveform images, a training set of raw ECG data, and/or a training set of pseudo-raw ECG signal data for all twelve leads. In all cases, known diagnosis data for the training set can be utilized as output data. The diagnosing function can utilize one or more neural networks to generate the diagnosis data from the pseudo-raw ECG signal data, measurement data, and/or waveform images. The diagnosis data generated by performing diagnosing function 4026 can include some or all of diagnosis data 4440, can include automatically generated treatment instructions based on the determined diagnosis, and/or can include prescription data such as an automatically generated prescription and/or recommended prescription based on the determined diagnosis.

Performing diagnosing function 4026 can utilize other information, such as additional information 4419, ECG classifier data 4420, and/or patient history data 4430, for example, by utilizing models trained on this other type of information as input labels. In some embodiments, other ECGs and/or other medical scans of the same patient are received as longitudinal data, and are also processed as discussed herein to generate some or all of the diagnosis data by utilizing the same or different model trained on corresponding types medical scans as discussed herein, and/or by utilizing a single model trained to process both the ECGs and additional medical scans as input to generate diagnosis data. Some or all of this additional information can be retrieved from a patient database corresponding to the patient, can be retrieved from the ECG database 4342, can be retrieved from a user account associated with the user that sent the captured image, and/or can be retrieved from the client device in the same or different transmission as the captured image.

In some embodiments, some or all of the diagnosis data is generated based on the measurement data itself, for example, based on determining one or more abnormal measurements and/or based on known rules for diagnosing ECGs based on measurement data 4443. For example, the diagnosis data can be a deterministic function of the measurement data 4443, and/or a partial diagnosis generated by utilizing the measurement data 4443 can supplement and/or be utilized to confirm or deny other diagnosis data generated by applying diagnosing functions on waveform images and/or pseudo-raw signal data.

In various embodiments, an ECG interpretation system 4002 includes at least one processor and a memory that stores operational instructions that, when executed by the at least one processor, cause the ECG interpretation system to receive, via a receiver, a captured image of an ECG printout. A waveform detection function is performed on the captured image to determine a plurality of locations of a plurality of ECG waveforms in the captured image. A plurality of waveform images are generated by partitioning the captured image based on the plurality of locations, where each of the plurality of waveform images includes one of the plurality of ECG waveforms. A plurality of pseudo-raw ECG signal data is generated by performing a signal reconstruction function on each of the plurality of waveform images, where each of the plurality of pseudo-raw ECG signal data corresponds to one of the plurality of waveform images. Diagnosis data is generated by performing a diagnosing function on the plurality of pseudo-raw ECG signal data. The diagnosis data is transmitted, via a transmitter, to a client device for display via a display device.

As discussed thus far, the ECG interpretation system 4002 can be utilized as an end to end automated service, where the diagnosis data generated automatically by the ECG interpretation system 4002 is transmitted back to the original client device from which the captured image was received. Similarly, the diagnosis data can be made available for access via a user account associated with the user that transmitted the captured image, a user account associated with the patient for whom the ECG was recorded, and/or a user account associated with a doctor or medical entity providing care for the patient for whom the ECG was recorded. In this fashion, the diagnosis data can be accessed by any client device 120 where a user is logged in to their user account. For example, the client device 120 can store application data associated with the ECG interpretation system 4002 to execute an application allowing the user to access their diagnosis information when logged into their user account. Alternatively, a third party messaging service, such as email, an SMS text-based messaging service, and/or internet-based messaging service can be utilized, where the captured image is received by the ECG interpretation system 4002 from an email address, phone number, or other handle associated with a user account, and where the diagnosis data is sent transmitted by utilizing the same messaging service to the same email address, phone number, or other handle associated with a user account.

ECG interpretation system 4002 can store, access, and/or maintain a database of user accounts that include corresponding user information and/or corresponding ECG printouts. The user account information can be stored in ECG database 4342, for example, as patient identifier data 4431 and/or retrieving entity identifier 4418. Alternatively or in addition, patient identifier data 4431 and/or retrieving entity identifier 4418 can include a unique identifier for a user account entry in the database of user accounts of the ECG interpretation system 4002. The user account can include a user login information and/or can indicate an email address and/or third party messaging service handle, identifying a user from whom a captured image is received via login to a user account, via an email from an email address identifying the user, and/or via a message via a third party messaging service via a handle identifying the user. Similarly, the user account can indicate to whom diagnosis data should be sent, and can be utilized to determine with user account the diagnoses data should be made available to via user login to the user account, to determine which email address an email that includes the diagnosis data should be sent to via email, and/or to determine which handle a message that includes the diagnosis data should be sent via a third party messaging service. The user account can store current and/or historical medical information for each user, user preference data for use of user interface 4077 for each user and/or for generation of formatted medical reports, captured images and corresponding diagnosis data generated for each user's use of the system, and/or other information for each user determined via interaction with user interface 4077. The user account can be utilized to generate one or more fields of an ECG entry 4452, and/or an ECG entry 4452 can be utilized to populate one or more fields of the user account.

In some embodiments, human review is determined to be necessary in generating the diagnosis data. For example, the ECG interpretation system 4002 can determine diagnosis data generated for a captured image requires human review based on corresponding confidence score data 4460 indicating or more probability values generated in generating the diagnosis data comparing unfavorably to one or more corresponding probability thresholds, in response to a random quality assurance process, in response to a request from a client device for a second opinion via user interface 4075, and/or in response to the ECG interpretation system otherwise determining human review is necessary. In some embodiments, all ECGs indicated as abnormal in the diagnosis data are designated for human review. In some embodiments, all diagnosis data corresponding to a rare condition that compares favorably to a rarity threshold, a time-sensitive condition that compares favorably to a time-sensitivity threshold, and/or a severe condition that compares favorably to a severity threshold, are designated for human review. In some embodiments, human review is never determined to be necessary, and the diagnosis data generated automatically by the ECG interpretation system 4002 is utilized.

As illustrated in FIG. 12F, the diagnosis data generated by performing the ECG processing function 4005 can correspond to partial and/or unconfirmed diagnosis data. The captured image of the ECG printout, reconstructed pseudo-raw signal data generated by performing the ECG processing function 4005, and/or the diagnosis data generated by performing the ECG processing function 4005 can be transmitted to a selected, second client device, for example, that is different from the client device from which the captured image was received. For example, the client device can be associated with a user in the user database, can correspond to a medical professional qualified to interpret ECGs, can correspond to an expert user in the user database, can correspond to an administrator of the ECG interpretation system 4002, and/or can correspond to a physician providing care for the patient for whom the ECG was recorded.

This client device can display some or all of this information via the user interface 4076. User interface 4076 can utilize features of user interface 4075, such as those discussed in conjunction with FIGS. 13D and/or 13E with regards to display of diagnosis data. User interface 4076 can utilize features discussed in conjunction with the medical scan assisted review system 102 and/or the medical scan annotating system 106 to prompt the user to review the ECG and/or the diagnosis data generated by the ECG interpretation system 4002, and to provide annotations, corrections, and/or additional information via interaction with the user interface 4076. The user can confirm the diagnosis, can provide edits to the diagnosis, and/or can further characterize the ECG to provide additional details. For example, if the diagnosis data generated by the ECG interpretation system 4002 only indicates that the ECG is abnormal and/or that the ECG includes at least one abnormal measurement, this diagnosis data can be sent to the user, who can review the ECG and provide additional diagnosis information, for example, indicating that the ECG corresponds to an atrial fibrillation. The user can interact with the user interface to indicate particular portions of the waveform that are abnormal and/or were utilized to determine the abnormality exists as annotation data to be included in the additional diagnosis data. The user can provide treatment steps and/or provide prescription medication details, for example, if the user corresponds to a physician of the user.

The user can indicate problems and/or corrections to the pseudo-raw signal data and/or any measurement data 4443. The user can determine that one or more models utilized by the ECG processing function 4005 be retrained and/or entered into remediation in response to detecting problems with the diagnosis data. In some embodiments, in response to a correction to the measurement data 4443, one or more coordinate pairs of the pseudo-raw signal data is automatically corrected to reflect the measurement correction to change intervals, amplitudes, and/or locations of one or more waves, and the graphical representation of updated pseudo-raw signal data is displayed via user interface 4076. Similarly the user can interact with the graphical representation of the pseudo-raw signal data to change one or more of the coordinate pairs based on clicking and dragging the coordinate to its desired position, where the shape of the waveform of the graphical representation of the pseudo-raw signal data changes accordingly to display updated pseudo-raw signal data, and/or where one or more measurements of measurement data 4443 is updated to reflect the changes to the one or more coordinate pairs. The pseudo-raw signal data can be overlaid upon corresponding waveform image 4014 as discussed in conjunction with FIG. 13E to aid the user in editing the positions of the coordinates making up the waveform of the pseudo-raw signal data to better characterize the waveform depicted in the captured image of the ECG printout.

The additional diagnosis data generated by the client device can be transmitted back to the ECG interpretation system 4002, and/or can be transmitted to the ECG database or other entity. A consolidation function 4006 can be performed on the additional diagnosis data and the partial diagnosis data to generate the final diagnosis. This can include replacing or supplementing the some or all of the partial diagnosis data with some or all of the additional diagnosis data to generate the final diagnosis data. The final diagnosis data to be sent back to the original client device from which the captured image was received.

FIGS. 13A-13E illustrate example embodiments of the user interface 4075 presented to the user in conjunction with use of a client device communicating with the ECG interpretation system 4002. The user interface 4075 can be displayed in conjunction with execution of a web application executed in a web browser displayed by a display device of the client device and/or in conjunction with execution of locally stored application data such as a mobile application associated with the ECG interpretation system 4002. The application can allow and/or require that the user create and/or login to a user account to interact with some or all of the features presented in FIGS. 13A-13E.

The client device and/or user account can correspond to the patient of whom the ECG printout was recorded, and/or can correspond to a medical professional or any other person providing care for the patient. For example, the patient can take or upload a picture and/or scan of their own ECG printout they received at a visit to a doctor's office or hospital and/or a picture taken of the display on the ECG monitor while the ECG monitor was recording their electrical activity. The patient can receive their diagnosis data from the ECG interpretation system 4002 in response and/or can designate a physician and/or other entity to receive the diagnosis data.

Alternatively, a physician or other medical professional can take and/or upload a picture and/or scan of the ECG printout with their own client device, can receive their diagnosis data from the ECG interpretation system 4002 in response and/or can designate that the diagnosis data be sent to a different entity. For example, a medical professional providing care for a patient can take or upload a picture and/or scan of the patient's ECG printout, a picture taken of the display on the ECG monitor, and/or a screenshot of the display on the ECG monitor. In particular, the doctor can utilize the ECG interpretation system 4002 if they are not adept at interpreting ECGs and/or if they encounter an ECG of a patient that is odd and/or difficult to interpret.

As another example, the client device can be associated with a first response medical professional providing emergency care for a patient outside of a normal hospital setting, for example, at the place where a patient undergoing an emergency is found and/or in an emergency transport vehicle such as an ambulance and/or helicopter. The first response medical professional can utilize the client device to take a picture of the display on an ECG monitor while the corresponding ECG machine is recording to the patient for automatic interpretation by the ECG interpretation system 4002. Alternatively the client device can connect to the ECG machine to display ECG readings recorded by the ECG machine on its own display device, and can automatically utilize the raw ECG readings and/or a screenshot of the ECG readings displayed on the display device of the client device as the captured image. The client device can be associated with the first response medical professional and/or the emergency transport vehicle can be equipped with the client device. The diagnosis data can be transmitted back the client device for display to the first response medical professional, for example, where the diagnosis data includes emergency care instructions to the first response medical professional based on abnormalities detected in the ECG waveforms. Alternatively or in addition, the diagnosis data can be transmitted to a database and/or client device associated with a hospital or other medical entity where the first response medical professional is taking the patient. This can allow medical professionals at the hospital to view the diagnosis data before the patient arrives at the hospital, enabling the medical professionals to prepare for the patients arrival, and/or ensuring they are ready to provide immediate care to the patient once they arrive based on results and/or treatment instructions included in the diagnosis data.

While FIGS. 13A-13E depict the presentation of the user interface via a display device of a mobile device, any display device associated with any client device, such as a personal computer, laptop, tablet, or other client device can display the user interface 4075. Features of the example user interface embodiments presented in FIGS. 13A-13E can be presented in any configuration, and other embodiments can include additional features instead of or in addition to some or all of the features presented in FIGS. 13A-13E to perform the same or different functions as discussed in conjunction with FIGS. 13A-13E.

FIG. 13A presents an example embodiment of a user interface 4075 presented to the user to prompt the user to generate and/or upload the captured image of the ECG printout. The user can elect to upload an existing captured image of the ECG printout from memory of the client device. The user can elect to use an image captured device 4012 coupled to the client device to generate the captured image. For example, if this option is selected, the client device can automatically send instructions to, or otherwise communicate with, the image capture device 4012, such as a camera coupled to the client device and/or a scanner communicating with the client device, to cause the image captured device 4012 to capture the image data. Once the captured image is uploaded and/or generated, the captured image can be transmitted to by the client device to the ECG interpretation system 4002 and/or to the ECG database 4342 for retrieval by the ECG interpretation system 4002.

In some embodiments, the client device 120 includes health monitoring capabilities that can measure heart rate, hearth rhythm, and/or other health data. For example, the client device 120 can correspond to a smart watch or other wearable device worn by the user that collects the health data, or can communicate with and/or receive data from a wearable device worn by the user that collects the health data. As another example, the client device 120 can communicate with or upload data from a user's pace maker device to retrieve ECG data, abnormal rhythm data, and/or other health data collected by the pace maker. The client device 120 can communicate with or upload data from other medical devices, for example, that specializing in capturing ECG data and/or heart rhythm data. This captured ECG data, heart rhythm data, and/or other health data can be utilized instead of or in addition to the captured image of an ECG printout, for example, as ECG data and/or patient history data 4430 utilized as input to the ECG processing function 4005 to generate the diagnosis. The user can elect to upload and/or automatically retrieve some or all of this health data via the user interface 4075 instead of or in addition to the captured image. This health data can be transmitted to by the client device to the ECG interpretation system 4002 and/or to the ECG database 4342 for retrieval by the ECG interpretation system 4002 instead of or in addition to the captured image, where the ECG processing function 4005 is performed only on this health data to generate the diagnosis data and/or where the ECG processing function 4005 is performed on this health data as patient history data 4430 in conjunction with the captured image to generate the diagnosis data.

FIG. 13B illustrates an embodiment where the user elected to utilize the image captured device 4012 to generate the captured image. For example, a camera of a mobile device implemented as the client device is automatically utilized to allow the user to take a picture of the ECG printout. The user can view the captured image and can elect to retake the image if needed and/or can elect to send the image as presented. In some embodiments, the client device can automatically detect whether the entirety of the ECG printout is included in the frame and/or can automatically detect whether the resolution and/or image quality of the ECG printout is satisfactory, for example, based on detecting the presence of the gridlines, based on detecting the presence of the required number of waveforms, and/or based on detecting the presence of all four borders of the printout within the image. In such embodiments, the user will not be permitted to take the picture and/or the user will be required to retake the picture if these criteria are determined not to be met.

FIG. 13C illustrates an embodiment of the user interface 4075 where the user can enter additional information to supplement the captured image of the ECG printout. For example, this can be entered in conjunction with the user creating information for their user account and/or the user can be prompted to enter additional information in response to generating and/or uploading the captured image as discussed in conjunction with FIGS. 13A and 13B. The user can enter health history, current medications, and/or current symptoms manually, for example, by answering a series of health history questions presented by the user interface 4075, and/or can elect to upload health history document, prescription documents, and/or other documents, where the client device extracts the relevant health history information from the document automatically. Past medical reports, such as report data 449 and/or 4449, can be uploaded by the user and/or can be automatically retrieved by the client device 120 and/or the ECG interpretation system 4002 from a medical scan database 342, ECG database 4342, and/or a patient database. Similarly, other data relevant to the patient stored by a medical entity, such as medical scans or past ECGs, or other entries of a medical scan entry 352 and/or ECG entry can be retrieved from medical records of the patient. For example, the user can enter information for their hospital and/or physician and/or can give permission to their hospital and/or physician to release their medical information to the ECG interpretation system 4002. Some or all fields of health history, current medications, current symptoms, and/or medical reports can be mandatory and/or optional. In some embodiments, none of this information is required, but any of this information provided by the user is transmitted to the by the client device.

The entered information by utilizing user interface 4075 of FIG. 13C and/or any subsequent prompts via user interface 4075 is sent by the client device 120 to the ECG interpretation system 4002 and/or to the ECG database 4342 for retrieval by the ECG interpretation system 4002. For example, this information can be utilized as patient history data 4430 for use as input to the ECG processing function 4005 in conjunction with the captured image to generate some or all of the diagnosis data. In particular, a patient's health history, current medications, current symptoms, or other medical documents can provide insight to diagnose the patient and/or to determine a cause of abnormal rhythms detected in the diagnosis data generated by performing ECG processing function 4005. For example, the diagnosis data can include specialized treatment data, prevention instructions, and/or prescription data for any abnormalities detected in the ECG determined based on this additional information of patient history data 4430.

FIGS. 13D and 13E present embodiments of displaying the diagnosis data received from the ECG interpretation system 4002 via user interface 4075 once the ECG printout and/or any additional information provided by the user is processed. FIG. 13D illustrates diagnosis data displayed as text, indicating a diagnosis of premature ventricular contractions. The diagnosis data can be presented to include any additional information presented in the diagnosis data such as treatment options, prescription data, information about how this diagnosis was detected in the ECG, confidence score data indicating probabilities that this diagnosis is accurate, pseudo-raw signal data and/or measurement data 4443 automatically. In some embodiments, the user can elect to view some or all of this additional information via selecting one or more corresponding options presented via the user interface 4075.

The user can elect to generate and/or view a formatted report for example as a PDF or other file format, where the report is generated by the client device 120 by utilizing the diagnosis data. Alternatively, the formatted report can be generated by and received from the ECG interpretation system 4002 in the diagnosis data automatically. The formatted report can utilize formatting preferences and/or other preferences to generate the formatted report, for example, indicated in the user account for the user and/or specified via other input to one or more other prompts presented via user interface 4075. The formatted report can correspond to report data 4449, and can include a processed or unprocessed captured image of the ECG printout; can include some or all of measurement data 4443; can include a graphical display of pseudo-raw signal data reconstructed by the ECG interpretation system 4002 for one or more leads, for example as shown in FIG. 12E as pseudo-raw ECG signal data 4016; can include annotations such as annotation data 4448 overlaid upon the to the pseudo-raw signal data or waveforms of the ECG printout itself, indicating abnormal rhythms, indicating measurement data 4443 and/or the P, Q, R, S and/or T wave, and/or indicating other significant features detected in the waveform of one or more leads; can include treatment data and/or prescription medication to be taken to mitigate the effects of the diagnosis; and/or can indicate any other diagnosis data 4440 generated by performing the ECG processing function 4005 and/or indicating other fields of a corresponding ECG entry 4452. Some or all of this information of the formatted report can be displayed in the same or different format via the interactive interface 4075.

The user can elect to view the reconstructed signals, as discussed in further detail in FIG. 13E. The user can elect to view the auto-generated measurements, where some or all of measurement data is displayed as text and/or is visually indicated on the waveforms of the pseudo-raw signal data and/or on the original and/or processed captured image of the ECG printout.

The user can elect to send their results their physician or other medical entity automatically, for example, based on the contact information or an account associated with the physician. This information can be indicated in the user's account or can otherwise be entered by the user, for example, where the user indicates an email address or other messaging handle for the physician via interaction with the user interface 4075 and where some or all of the diagnosis data is transmitted in a message via email or other messaging service to the physician accordingly. In some embodiments, the physician can login to their own user account and can view diagnosis data of one or more of their patients in a similar fashion as discussed in conjunction with FIGS. 13D and 13E via their own interactive interface 4075 and/or 4076. In some embodiments, the diagnosis data is automatically transmitted to a client device associated with the physician by the ECG interpretation system 4002 once it is generated based on physician information for the patient in their user account.

The user can elect to send a prescription prescribed based on the diagnosis data to a pharmacy immediate and/or as soon as it is available. their physician In some embodiments, a prescription is generated automatically in the diagnosis data generated by performing ECG processing function 4005 and/or is received from a physician that reviewed the diagnosis data. For example, the prescription can be generated via interaction with user interface 4076 in generating the additional diagnosis data as discussed in conjunction with FIG. 12F. Alternatively or in addition, the prescription can be generated by a client device associated with the user's physician in response to the user electing to send the diagnosis data to their physician. The diagnosis data can include one or more recommended prescriptions and the physician interacting with user interface 4076 and/or the user's physician that received the diagnosis data can select from the one or more recommended prescriptions in the diagnosis data. The user account can include pharmacy information and/or the user can enter pharmacy information via the user interface 4075. The prescription can be automatically sent to the pharmacy indicated in the user account once it becomes available.

The user can elect to request a second opinion, for example, in response to determining the results in the diagnosis data is unconvincing, incomplete, and/or in response to determining additional review is necessary based on the review of the diagnosis data. This can prompt the transmission of the diagnosis data to the client device for additional review to receive edits and/or additional diagnosis data as illustrated in FIG. 12F. The user selected for the second opinion can be automatically determined by the ECG interpretation system 4002 and/or can be selected by the user.

The user can elect to review more information about their diagnosis and/or treatment of their diagnosis, for example, where the client device displays medical articles and/or websites specific to a condition indicated in their diagnosis data. Internet links to medical articles and/or websites, and/or documents that include the articles or additional information about the diagnosis can be selected by the ECG interpretation system 4002 based on the diagnosis data for transmission in conjunction with the diagnosis data, where the user is automatically displayed the links and/or the documents via the interactive interface 4075. The user can select a link to be routed to a corresponding article and/or website for display to the user via a web browser.

FIG. 13E illustrates an example embodiments of the user interface 4075 displayed in response to user selection to view the reconstructed signals and/or displayed automatically. The reconstructed signals can include a graphical representation of the pseudo-raw signal data generated by performing the ECG processing function 4005. As shown in FIG. 13E, annotation data 4448 indicating diagnosed premature ventricular contractions or other waveform features characterizing the diagnosis can be visually indicated, and/or other features such as the normal beats can be visually indicated. The measurement data and/or other annotation data can similarly can be indicated in the waveform, where corresponding portions of the waveform are highlighted, displayed in a different color, outlined, bolded, circled or surrounded by a segmented shape, or otherwise visually indicated.

The waveforms for some or all twelve leads can be displayed one at a time or all at the same time. For example, the user can elect to advance to the next lead, and each lead can be displayed one at a time. The ordering of the leads and/or how many lead waveforms are displayed in a single view can be set based on user preferences and can be stored as user account data and/or the ordering of the leads can be preset. Alternatively, the first lead displayed and/or the ordering of leads displayed can be determined automatically by the ECG interpretation system 4002 in performing the ECG processing function 4005, for example, where lead waveforms with most abnormal findings, lead waveforms with most significant findings, and/or lead waveforms with most visually obvious findings are displayed first.

The user can elect to view the original captured image of a cropped, single waveform such as waveform image 4014 corresponding to the currently displayed waveform and/or can display the entirety of the captured image of the ECG printout in the same or different view as the reconstructed signal. Alternatively, some or all of the processed and/or unprocessed captured image is displayed automatically. The annotation data 4448 can similarly be displayed as overlaid upon the waveform detected in the waveform image 4014. In some embodiments, the pseudo-raw signal data can be overlaid graphically on top of the corresponding waveform image 4014, for example in a different color from the color of the waveform in the waveform image. Alternatively, the pseudo-raw signal data and corresponding waveform image 4014 can be displayed in adjacent views of the user interface.

The user can elect to view an example of one or more normal signals, for example, corresponding to one or more leads currently being viewed. The normal signal can be the same normal signal for every user. In some embodiments, the normal signal can be generated by the ECG interpretation system 4002, for example, by detecting the abnormal features of the waveform in the pseudo-raw signal data and by removing the abnormal features from waveform in the pseudo-raw signal data, for example, where an inverse signal corresponding to the portions of the waveform that are abnormal is added to the pseudo-raw signal data to generate pseudo-normal signal data. The pseudo-normal signal data can be presented in conjunction with the pseudo-raw signal data and/or the waveform image 4014, for example, in an adjacent view. Alternatively, the pseudo-normal signal data can be overlaid graphically on top of the corresponding waveform image 4014 and/or the pseudo-raw signal data, for example, in a different color from the color of the waveform in the waveform image and/or from the color of the graphical representation of the pseudo-raw signal data.

FIG. 14 presents a flowchart illustrating a method for execution by an ECG interpretation system 4002 that stores executable instructions that, when executed by at least one processor, cause the ECG interpretation system 4002 to perform the steps below.

Step 5002 includes receiving, via a receiver, a captured image of an ECG printout. Step 5004 includes performing a waveform detection function on the captured image to determine a plurality of locations of a plurality of ECG waveforms in the captured image. Step 5006 includes generating a plurality of waveform images by partitioning the captured image based on the plurality of locations, where each of the plurality of waveform images includes one of the plurality of ECG waveforms. Step 5008 includes generating a plurality of pseudo-raw ECG signal data by performing a signal reconstruction function on each of the plurality of waveform images, where each of the plurality of pseudo-raw ECG signal data corresponds to one of the plurality of waveform images. Step 5010 includes generating diagnosis data by performing a diagnosing function on the plurality of pseudo-raw ECG signal data. Step 5012 includes transmitting, via a transmitter, the diagnosis data to a client device for display via a display device.

In various embodiments, the ECG printout was generated by an ECG machine based on electrical activity recorded by the ECG machine, and the captured image was generated by a utilizing an image capture device to generate the captured image from the ECG printout. In various embodiments, the image capture device corresponds to a camera. In various embodiments, the camera is coupled to a mobile device, and the captured image is transmitted to the ECG interpretation system by the mobile device. In various embodiments, the client device that receives the diagnosis data corresponds to the mobile device. In various embodiments, the image capture device corresponds to a scanner.

In various embodiments, the waveform detection function utilizes a computer vision model trained on a training set of waveform images. In various embodiments, the waveform detection function utilizes a computer vision model trained on a training set of ECG printouts. In various embodiments, the waveform detection function utilizes standardized layout information, where the standardized layout information indicates relative positions of waveforms in standard ECG printouts. In various embodiments, the standardized layout information indicates relative locations of exactly twelve waveforms. Each of the exactly twelve waveforms corresponds to one of twelve ECG leads. The plurality of waveform images includes exactly twelve waveform images corresponding to the twelve ECG leads. In various embodiments, the waveform detection function utilizes standardized formatting feature information, where the standardized formatting feature information indicates at least one relative position of at least one additional feature in standard ECG printouts. Performing the waveform detection function includes detecting the at least one additional feature in the ECG printout.

In various embodiments, the signal reconstruction function utilizes a computer vision model trained on a training set of waveform images. In various embodiments, the signal reconstruction function determines a plurality of discrete points for one of the plurality of waveform images, where a corresponding one of the plurality of pseudo-raw ECG signal data includes the plurality of discrete points. In various embodiments, the diagnosing function is trained on a training set of raw ECG signal data, where each raw ECG signal data in the training set includes discrete points characterizing the raw ECG signal data. In various embodiments, the signal reconstruction function determines a pseudo-raw waveform shape for one of the plurality of waveform images, where a corresponding one of the plurality of pseudo-raw ECG signal data includes the pseudo-raw waveform shape. In various embodiments, the diagnosing function is trained on a training set of raw waveform shapes corresponding to raw ECG signal data. In various embodiments, the training set of raw waveform shapes corresponds to image data that includes raw waveform shapes recorded by at least one ECG machine.

In various embodiments, the diagnosing function is trained on a training set of raw ECG signal data. Each raw ECG signal data in the training set includes raw ECG signal data for each of twelve ECG leads, and the plurality of pseudo-raw ECG signal data includes twelve pseudo-raw ECG signal data corresponding to the twelve ECG leads. The diagnosing function is performed on the twelve pseudo-raw ECG signal data as input to generate the diagnosis data.

In various embodiments, performing the diagnosing function on the plurality of pseudo-raw ECG signal data includes generating twelve sub-diagnosis data, where each of the twelve sub-diagnosis data is generated by performing one of twelve inference functions on a corresponding one of twelve pseudo-raw ECG signal data. Each of the twelve inference functions corresponds to one of twelve ECG leads and is trained on a training set of raw ECG signal data for the corresponding one of the twelve ECG leads. A final inference function is performed on the twelve sub-diagnosis data to generate the diagnosis data.

In various embodiments, the captured image is received from the client device, the ECG printout corresponds to a patient, and the client device is associated with the patient. In various embodiments, the client device is associated with a medical professional responsible for the patient. In various embodiments, the ECG printout is received in an first email transmission from a first email address associated with a requestor to a second email address associated with the ECG interpretation system, and the diagnosis data is transmitted in a second email transmission from the second email address to the first email address. In various embodiments, the requestor is a user of to the client. In various embodiments, the second email transmission includes a document for display to the requestor via the client device. The document includes the diagnosis data and the plurality of pseudo-raw ECG signal data. In various embodiments, the diagnosis data is displayed via the display device in conjunction with the captured image. In various embodiments, the diagnosis data is displayed via the display device in conjunction with the plurality of pseudo-raw ECG signal data via a user interface. In various embodiments, the diagnosis data is displayed via the display device in conjunction with the plurality of pseudo-raw ECG signal data via a user interface.

In various embodiments, the diagnosis data indicates at least one abnormality in at least one of the plurality of pseudo-raw ECG signal data. The at least one abnormality is visually indicated in the display of the at least one of the plurality of pseudo-raw ECG signal data. In various embodiments, normal pseudo-raw ECG signal data is generated by removing the at least one abnormality from the at least one of the plurality of pseudo-raw ECG signal data. The normal pseudo-raw ECG signal data is displayed via the display device in conjunction with the diagnosis data and the plurality of pseudo-raw ECG signal data.

In various embodiments, as discussed in further detail in conjunction with FIGS. 15A-15C, the method includes the following additional steps, which can be performed in addition to or instead of some or all of the steps of FIG. 14. The additional steps include receiving, via the receiver, a captured image of a patient's skin. The additional steps further include generating second diagnosis data by performing a second diagnosing function on the captured image of the patient's skin, where the second diagnosing function utilizes a computer vision model trained on a plurality of images of skin corresponding to a plurality of skin conditions. The additional steps further include transmitting, via the transmitter, the second diagnosis data to the same or different client device for display via a display device.

While FIGS. 12A-12F, FIGS. 13A-13E, and FIG. 14 illustrates embodiments specific to ECGs, some or all of the functionality of the ECG interpretation system 4002 and/or the user interfaces 4075 and/or 4076 displayed by client devices 120 can similarly be applied to any other captured images that include medical information. FIGS. 15A-15C illustrate an embodiment of a captured image processing system 4004, which can utilize features of, be integrated within, and/or communicate with the ECG interpretation system 4002 and/or one or more other subsystems 101. Instead of or in addition to generating diagnosis data based on images of ECG printouts, diagnosis data can be generated by the captured image processing system 4004 based on captured images of other medical information. As illustrated in FIG. 15A, a captured image can be received from a client device. The captured image processing system 4004 can perform a processing function 4008 to generate diagnosis data for the captured image, which can include some or all of the diagnosis data 440 and/or diagnosis data 4440. The processing function 4008 can include any of the medical scan analysis function and/or inference function discussed herein, and/or can utilize a computer vision model trained on one or more types of captured images and corresponding diagnosis data.

In some embodiments, the captured image processing system 4004 first performs a image classifier function 4007, for example, to determine an anatomical region of the image, to determine anatomical features in the image that need to be diagnosed, and/or to otherwise classify the image into one of a plurality of image types. Once the image type is determined by performing the image classifier function 4007 on the captured image, one of a plurality of different processing functions 4008, each corresponding to one of the plurality of image types, can be selected for performance on the image data. In some embodiments, the captured image is pre-processed with filters to change brightness, contrast, orientation, and/or to crop the image before the image classifier function 4007 and/or processing functions 4008 is applied.

The diagnosis data generated by performing the processing functions 4008 can be transmitted to the same and/or different client device for display via an interactive interface 4077. The captured image and/or diagnosis data can be transmitted to medical scan database 342. For example, the medical scan database can include entries for captured images of medical documents and/or captured images of the body taken by a camera as discussed herein, where image data 410 corresponds to one or more captured still images and/or a captured video. Alternatively or in addition the captured image and/or diagnosis data can be sent to ECG database 4342 and/or a different database that stores captured images, diagnosis data, and/or some or all of the fields of entries of medical scan database 342 and/or ECG database 4342. The captured image and/or diagnosis data can be alternatively or additionally be transmitted to any other medical entity such as a doctor of the patient and/or to another client device to generate additional diagnosis data as discussed in conjunction with FIG. 12F, for example, where user interface 4076 is utilized to generate additional diagnosis data corresponding to supplemental information and/or corrections to the diagnosis data via human review, and where final diagnosis data is generated and transmitted based on the additional diagnosis data.

In some embodiments, captured images received by the captured image processing system 4004 correspond to captured images such as photos or scans of physical printouts of any of the medical scans discussed herein, captured images such as photos or scans of physical printouts of any of the report data discussed herein, and/or captured images such as photos or scans of any printouts for any medical information generated by a machine and/or a medical professional. In such embodiments, the captured image can be processed by utilizing a computer vision model and/or natural language model for example, as discussed in conjunction with the medical scan image analysis system 112, the medical scan diagnosing system 108, and/or the medical scan natural language analysis system 114. The image classifier function 4007 and/or processing function 4008 can utilize any of the medical scan analysis function discussed herein. The captured image can be pre-processed by utilizing additional image processing to best capture and/or enhance the pertinent information of the scan and/or report in the printout. The image classifier function 4007 can determine one of a plurality of medical scan types and/or anatomical regions by utilizing the input quality assurance function and/or another computer vision model trained on captured images of medical scans with output labels indicating scan type, anatomical region, and/or other scan classifier data 420. The processing function 4008 can correspond to a medical scan inference function 1105 of the corresponding category, and/or can be trained on a training set of captured images of physical printouts of medical scans of the corresponding category with known diagnosis data 440 as output labels. Alternatively, some or all of the medical scans in the training set can correspond to image data 410 of the original medical scans, rather than a captured image of a physical printout of the medical scan.

Alternatively or in addition, captured images of physical, anatomical features of a patient, taken by a camera, can be similarly be processed by the captured image processing system to generate diagnosis data. For example, a patient can utilize a camera on their mobile device to take a picture of a concerning abnormality on their skin and/or an externally observable abnormality that is otherwise visually observable via the human eye and/or via the image capture device 4012 communicating and/or coupled to their client device. This captured image can be transmitted by the client device to the captured image processing system 4004 for processing. The patient and/or their dermatologist or other doctor can receive and view diagnosis data generated by the captured image processing system 4004 in response via the same or different client device.

The image classifier function 4007 can detect the anatomical region, type of bodily tissue and/or bodily fluid captured, and/or other classifying information for the captured image to determine the processing function 4008. For example, the image classifier function can utilize a computer vision model trained to detect anatomical regions of the human body and/or types of bodily tissue and/or bodily fluid in the captured image, for example, where the computer vision model is trained on a plurality of captured images of the human body with and/or without abnormalities included, where the output labeling data indicates the anatomical regions, type of bodily tissue, type of bodily fluid, and/or other classifying information in the captured image. Alternatively or in addition, the image classifier function 4007 can be utilized to distinguish between captured images of the body by a camera and images corresponding to medical documents such as captured images of printout of medical scans, ECG printouts, or medical reports.

Some or all processing functions 4008 can be trained on captured images corresponding to the classifying type. For example, one processing function can be trained to process pictures of the hand and a second processing function can be trained to process pictures of the back. As another example, one processing function can be trained to process pictures of skin conditions to provide dermatological diagnosis, another processing function can be trained to process pictures of the inside of the mouth to provide a dental and/or orthodontal diagnosis, and/or another processing function can be trained to process pictures of the eye to provide an ophthalmological diagnosis. As another example, one processing function can be trained to diagnose pictures of bruised skin, another processing function can be trained to diagnose pictures of skin that include acne, another processing function can be trained to diagnose pictures of skin with a rash, another processing function can be trained to diagnose pictures of skin with a rash, another processing function can be trained to diagnose pictures of skin with a cuts and/or abrasions, and/or another processing function can be trained to diagnose pictures of skin with a burn. Some processing functions 4008 can be trained to generate RECIST data for moles and/or skin lesions in captured images of the skin, for example, by utilizing one or more measurement functions of the lesion tracking system 3002 of FIGS. 16A-16D. Each processing function 4008 can utilize a computer vision model trained to diagnose conditions of the corresponding type of image, for example, where each processing function 4008 is trained on a training set of images of the corresponding type as input data and on corresponding diagnosis data as output labels.

In some embodiments, multiple processing functions 4008 are performed in response to output of the image classifier function 4007 indicating the captured image falls under multiple categories. Alternatively or in addition, multiple processing functions 4008 are performed in accordance with a hierarchy of processing functions 4008. For example, a first processing function 4008 trained to detect skin conditions is performed first on the captured image in response to determining the captured image is a picture of the skin. The diagnosis data generated by the first processing function can indicates a rash, and second processing functions 4008 trained to diagnose particular types of rashes can be selected to be performed next on the captured image to provide a more detailed diagnosis. In some embodiments, a single processing function 4008 is performed on all captured images, and/or no image classifier function 4007 is performed.

In some embodiments, the user can provide additional information describing the condition. This additional information can correspond to what part of the body the image includes, for example if the image is very zoomed in; can include image measurement and/or other observations of the abnormal condition taken by the user; can include symptoms such as pain and/or itchiness of a skin condition and/or other symptoms; can include current medication being taken, medical history, family medical history, and/or can include other information that can be entered via user interface 4077 by the user for transmission to the captured image processing system 4004 in conjunction with the captured image. Some or all of the additional information can correspond to information entered by the user to user interface 4075 as discussed in conjunction with FIG. 13C. This additional information can correspond to and/or can be utilized to determine patient history data 430 and/or one or more other fields of a corresponding entry in the medical scan database. This can be utilized by the image classifier function 4007 to determine which processing functions 4008 are performed on the captured image. This can also be utilized as input to one or more processing functions 4008 to generate some or all of the diagnosis data, for example, where a processing function 4008 utilized similar types of additional data as input labels in the training data to train the processing function 4008.

The captured image can correspond to a single, still, image, photograph and/or other picture, for example, received as a PNG, JPEG, or other image format for a single image. In some embodiments, a set of multiple captured images can be received, for example, corresponding to multiple pictures taken of an abnormal condition appearing on the same or different part of the body from the same or different angle. The same or different processing function 4008 can be performed on each of the set of captured images, and diagnosis data generated for each of the set of multiple captured images can be used in conjunction to generate the diagnosis data.

In some embodiments, the set of multiple captured images corresponds to temporal data taken over time, where the captured images show a change in the condition and/or or lack in change in the condition over time. The processing function 4008 can generate diagnosis data based on a detected and/or measured change in the condition and/or in the amount of time elapsed between captured images. For example, the processing function 4008 can utilize the lesion tracking system 3002 of FIGS. 16A-16D to generate diagnosis data that includes lesion measurement data and/or lesion tracking data. In particular, the processing function 4008 can be performed on pictures of skin lesions and/or moles on skin over time, where measurement change data is generated in generating the diagnosis data and/or where RECIST data is included in the diagnosis data. In some embodiments, measurement data and/or measurement change data is applied to pixel values and/or an established color in the captured image and/or multiple captured images taken over time to determine color and to track the change in color over time.

The client device can transmit video data, for example, to capture the abnormal condition from the different angles and/or different parts of the body, where some or all frames of the video are processed as a set of multiple captured images. Alternatively, the abnormal condition can correspond to a motion that can be captured by video but not by a still image. For example, an abnormal twitch, shaking, reflexive movement, rate of flow of a bodily fluid, dilation of pupils or other eye movement, and/or other bodily motion that can be captured via video can be included in the video data. The motion can be tracked and/or measured over the multiple frames in performing the processing function 4008 to generate the diagnosis data. For example, the processing function 4008 can be trained on training data that includes video data and/or includes a plurality or frames as input labels and includes corresponding diagnosis data as output labels.

As another example, a first response medical processional can utilize a camera on their mobile device and/or other client device to take a to take one or more pictures of externally observable medical conditions such as a severe wound that requires emergency care, a severe allergic reaction that requires emergency care, and/or any other externally observable condition that can be captured via a camera and/or another and/or via the image capture device 4012 communicating and/or coupled to the client device of the first response medical processional in a single image or a set of images. In some embodiments, the medical processional can utilize a camera on their mobile device and/or other client device to take a video to better capture the externally observable medical conditions and/or to capture motion-based conditions such as a seizure, a person who is chocking, a rate of blood loss from a wound, eye dilation or eye movement, or other condition that is observable as motion over multiple frames. In such embodiments, the image capture device 4012 can include a radiological medical imaging device or other specialized medical imaging equipment instead of or in addition to a camera. The client device can transmit the captured image to the captured image processing system 4004 for processing, and the diagnosis data can be sent back to the first response medical processional in conjunction with emergency care instructions based on the diagnosis to aid the first response medical processional in providing care. Alternatively or in addition, the captured images and/or the diagnosis data can be sent to the hospital and/or medical entity the patient is routed to directly for view by a medical professional at the hospital before the patient arrives, allowing the medical professional to provide specialized care based on the diagnosis data.

As another example, a bystander observing a person undergoing a medical emergency can utilize a camera on their mobile device, or on the mobile device of the person, to take one or more picture and/or a video of the severe, externally observable medical condition. The mobile device can similarly transmit the at least one picture and/or video to the captured image processing system 4004, and the captured image processing system 4004 can automatically an alert an emergency response entity and/or send the diagnosis data, emergency care instructions, and/or captured images to a first response medical processional already en route to respond to the emergency, to aid the first response medical processional to provide specialized care once they arrive. The bystander can utilize the same and/or different mobile device to call 911. In some embodiments, the pictures and/or diagnosis data generated by the captured image processing system 4004 can be automatically transmitted directly to an emergency response service in response to the bystander utilizing the mobile device to call 911. In some embodiments, the mobile device can automatically prompt the bystander to use the camera to take one or more pictures for automatic transmission to the captured image processing system 4004 in response to detecting the bystander utilized the mobile device to call 911.

As another example, one or more home surveillance cameras, cameras mounted on vehicles, public infrastructure surveillance cameras, and/or cameras capturing a stream of image can automatically determine if image data of an emergency medical condition has been captured, for example, by utilizing the captured image processing system 4004 on a stream of image data captured by one or more cameras. For example, a person having a seizure, a person who is bleeding and/or has been severely wounded, a fight or other dangerous activity that did or could lead to injury, a person who has undergone an major fall or major collision, a person who is choking, or another person undergoing a medical emergency can automatically be detected over multiple images in the video stream. In some embodiments, single frames are processed individually, and a major wound, injury, or emergency condition can be detected in the single frame. When a person with an emergency medical condition is automatically detected in a single image and/or in video, an emergency response entity can automatically be alerted to the location of the emergency. The diagnosis data, captured image, and/or emergency care instructions generated by the captured image processing system 4004 can be transmitted to a client device associated with a first response medical professional routed to the location of the emergency, allowing the first response medical professional to be prepared to give specialized care.

While FIG. 15A depicts a single client device, any number of different client devices can send any number of captured images to the captured image processing system 4004, and the same or different one or more client devices can receive the diagnosis data generated by the captured image processing system 4004 for the captured image. As discussed in conjunction with the ECG interpretation system 4002, the diagnosis data can be sent in accordance with an email address or messaging handle associated with a user account utilized to transmit the captured image. The captured image processing system 4004 can store, access and/or manage a database of user accounts which can include the same or different information as the database of user accounts stored by and/or accessed by the ECG interpretation system 4002. The database of user accounts can similarly store current and/or historical medical information for the user, user preference data for use of user interface 4077, captured images and corresponding diagnosis data generated for the user's use of the system, and/or other information determined via interaction with user interface 4077. While FIG. 15A depicts communication between the client device 120 and captured image processing system 4004 via network 150, in other embodiments, the client device can store application data for some or all of one or more processing functions 4008 and/or the image classifier function 4007. For example, the client device 120 of FIG. 15A can locally execute the application data to execute ECG processing function 4005 locally on captured images taken by or uploaded to the client device and to generate diagnosis data automatically in response.

FIG. 15B illustrates an example embodiment of a user interface 4077 displayed via the client device 120 in conjunction with capturing and/or preparing the captured image and/or other information for transmission to the captured image system. Some or all of the features presented and/or layout presented can be the same and/or different in various embodiments of user interface 4077. The user can upload to the client device and/or capture a picture via a camera of the client device to generate the captured image for transmission to the captured image processing system 4004. The captured image can be displayed to the user as depicted in FIG. 15B, and the user can enter additional information before transmission, to be sent with the transmission of the photo. The user can elect to utilize the camera of the client device itself to take and/or retake photos as needed, as discussed in conjunction with user interface 4075 of FIG. 13B. In the example depicted in FIG. 15B, the captured image includes a picture of the user's hand with an abnormal condition 4091.

The user can be prompted to and/or can elect to indicate the abnormality in the captured image, for example, by interacting with the captured image via user interface 4077 to generate location data for the abnormal conditions by circling and/or drawing one or more segmented polygons around one or more portions of the abnormal condition and/or by otherwise selecting one or more pixels that correspond to the portions of the image that correspond to the abnormal condition. For example, the locations of two separate portions of an abnormal skin condition 4091 as presented in FIG. 15B can each be selected by the user. The location data for the abnormal condition can be transmitted in conjunction with the captured image, and can be utilized by the captured image processing system 4004 to localize the abnormality in the captured image. In some embodiments, this information is not entered by the user, and/or the captured image processing system 4004 automatically localizes the abnormality.

The user can be prompted to and/or can elect to select an anatomical region corresponding to the image. For example, the user can indicate that the captured image corresponds to the user's left arm and/or can indicate that the abnormality is included on the skin of the user's left hand. This can be utilized by the captured image processing system 4004 to determine the location of the abnormality, which can aid in generating diagnosis data if the condition is always localized in a certain anatomical region and/or can aid in performing the image classifier function 4007, for example, where the captured image of FIG. 15B is processed by performing a processing function 4008 trained to diagnose skin conditions in response to the user indicating the captured image corresponds to skin and/or where the captured image of FIG. 15B is processed by performing a processing function 4008 trained to process images of hands and/or arms in response to the user indicating the abnormality is included on the left hand and/or in response to the user indicating the entire arm is included in the captured image. In some embodiments, for example, if the captured image is very zoomed in on skin and it is visually unclear which part of the body the picture is taken of, this information can be very helpful in localizing the anatomical region of the abnormality. In other embodiments, the user does not select an anatomical region, and/or the captured image processing system 4004 automatically detects a hand in the captured image to determine the captured image is taken of the hand, and/or the captured image processing system 4004 automatically detects skin in the captured image to determine the captured image is taken of the skin.

The captured image can include a scale marker 4092, which as depicted in FIG. 15B, corresponds to a quarter. The scale marker 4092 can correspond to any marker of a known size and/or shape, and can have known markings and/or other known visual features that make it easily detectable by processing functions of the captured image processing system 4004. The user interface can include instructions for selection of and/or placement of the scale marker 4092 in the image, for example, displaying a prompt that states “Include a quarter in the image on top of the skin in the vicinity of the skin condition.” In some embodiments, the scale marker is placed on the skin and/or otherwise on the body, and/or the scale marker can be placed next to the body within the image. In some embodiments, the scale marker 4092 is a commonplace item with known size, such as a quarter. In some embodiments, the scale marker 4092 is a specific marker and/or two dimensional printed logo or other image delivered to the user and/or downloaded to the same or different client device and printed by the user on paper in a known size. In some embodiments, the user can select from a set of scale marker options, and can select which scale marker is included by electing to enter scale information via the user interface 4077. In some embodiments, the user can utilize any item or printed image as the scale marker, and can, for example take other captured images of the scale marker and/or provide measurements for the scale marker. In some embodiments, the user interface 4077 presents size, color, and/or reflectivity requirements for the scale marker, and may prompt the user to utilize multiple scale markers that meet different sets of size, color, and/or reflectivity requirements. In some embodiments, the user can interact with the captured image to select the location of the scale marker 4092 in the captured image, where this indicated location of the scale marker is utilized by the image classifier function 4007 and/or the processing function 4008 in detecting the scale marker in the image.

Performance of the image classifier function 4007, the processing function 4008, or another function performed on the captured image that utilizes a computer vision model trained to detect the scale marker 4092, can be utilized to detect in the captured image and/or utilize the scale marker 4092. The captured image processing system 4004 can utilize known dimensions and/or known size of the scale marker 4092 to determine established scale information for the captured image, for example, based on dimensions and/or size of the scale marker 4092 in relation to the captured image. The established scale information can be utilized in generating diagnosis data, in performing one or more lesion measurement functions, and/or to determine size and/or portions of the body included in the image. Alternatively or in addition, the image classifier function 4007 and/or the processing function 4008 can determine pixel color data of the scale marker detected in the captured image, and can compare the pixel color data to known color information and/or known reflectivity information of the scale marker, for example, to establish lighting conditions in the captured image and/or to otherwise establish baseline lighting and/or color data for the image. In particular, if color is an important feature in diagnosing the abnormal condition, the established lighting and/or color information can be utilized to determine how the colors and/or brightness in the captured image could be distorting true color and/or brightness of the abnormal condition.

In various embodiments, the pre-processing of the image data includes adjusting color and/or brightness in the entire image by a factor necessary to adjust the color and/or brightness of the scale marker in the captured image to a preset baseline color and/or brightness. Alternatively or in addition, the pre-processing of the image data includes adjusting scale of the entire image by a factor necessary to adjust the size of the scale marker in the captured image to a known baseline size.

In some embodiments, the client device can locally determine whether the scale marker is detected in the captured image before transmission, and/or can determine if the resolution, size, color, and/or brightness of the scale marker as presented in the image indicates that lighting conditions, resolution, sizing, and/or other conditions of the photo will be sufficient for processing. In some embodiments, the user can be prompted to retake the photo if the size of the scale marker as detected in in the captured image compares unfavorably to a threshold, if the resolution and/or sharpness of the scale marker as detected in in the captured image compares unfavorably to a threshold, and/or if the brightness and/or color of the of the scale marker as detected in in the captured image compares unfavorably to a threshold. In some embodiments, the user is prompted with instructions to correct the problem, for example, where a prompt such as “please retake the photo in a brighter room” is presented in response to the brightness and/or color of the of the scale marker as detected in in the captured image comparing unfavorably to the threshold.

Instead of or in addition to utilizing a scale marker 4092, the user can manually enter information via user interface 4077 that can be utilized to determine the established scale data and/or the established color and/or brightness data. For example, the user can be prompted to measure one or more dimensions of or more abnormalities or other features in the captured by utilizing their own measuring device. The user can indicate endpoints of the corresponding measured dimensions in the captured image by interacting with the captured image via the user interface 4077, and the captured image processing system 4004 can utilize this information to determine the established scale data. The user can be presented with a plurality of color options and can select one or more color that most closely matches one or more colors of the abnormalities when viewed with the naked eye. The user can indicate locations of each one or more color of the abnormality in the captured image data by interacting with the captured image via the user interface 4077, and the captured image processing system 4004 can utilize this information to determine the established color data and/or brightness data.

The user can enter additional observations and/or symptoms to be sent to the captured image processing system 4004. For example, the user can enter natural language text describing observations and the captured image processing system 4004 can perform a natural language processing function can utilize a natural language model, for example, by utilizing the medical scan natural language analysis system 114, to extract key terms from and/or interpret some or all of the natural language text. Alternatively or in addition, the user interface can present a series of questions to the user, and the answers of the series of questions can be transmitted to the captured image processing system 4004. In some embodiments, a decision tree of prompts can be stored locally by the client device and/or can be utilized by the captured image processing system 4004 to determine the next question based on one or more answers to one or more previous questions, for example, where each answer is transmitted to the captured image processing system 4004 and the next question is received from the captured image processing system 4004 based on the previous answer. For example, questions such as “does the skin condition burn?”, “does the skin condition itch?”, “does the skin condition feel painful when pressure is applied?”, “how long has the skin condition been visible?”, “how much larger has the skin condition grown in the last 24 hours?”, and/or other questions presented to the user to provide additional information utilized to generate diagnosis data.

Alternatively or in addition, the user can be presented with drawings and/or captured images of abnormal conditions that the user's condition may correspond to, based on answers to questions so far, and the user can be prompted to select one or more images that look most similar to their condition. The known diagnosis for these images can be utilized to generate diagnosis data for the user. The answers to these questions can also be utilized to determine established scale information and/or established color information and/or brightness information for the captured image received from the user.

In some embodiments, some or all of the questions are determined by the captured image processing system 4004 after the captured image has been received and after diagnosis data has been generated, for example, where the questions are determined based on findings in the diagnosis data and/or missing information from the diagnosis data. In some embodiments, the user is prompted to take additional captured images, for example, with correction instructions based on problems with the prior captured image and/or with instructions to take pictures of additional areas of the body based on the diagnosis. The user can be prompted to wait a fixed amount of time, such as 24 hours, to retake one or more pictures, for example, where a measurement change function can be applied to the abnormal condition detected in the images over time to determine if the abnormal condition is growing and/or shrinking with time, if the color of the abnormal condition is changing with time, and/or if and/or becoming more or less severe. This can be utilized by the captured image processing system 4004 to generate additional diagnosis data for the patient after initial diagnosis data has already been generated and transmitted.

FIG. 15C illustrates an example of embodiment of user interface 4077 presented to the user in response to receiving the diagnosis data from the captured image processing system 4004. The user interface 4077 of FIG. 15C can include some or all of the features of the user interface 4075 discussed in conjunction with FIGS. 13D and/or 13E. Some or all of the features of user interface 4077 presented in FIG. 15C can be presented to medical professionals, for example, if the captured image and/or diagnosis data is sent to a medical professional providing care to the user, a medical professional selected to provide a second opinion, and/or a medical professional providing additional diagnosis data utilized by the captured image processing system 4004 to generate final diagnosis data.

The user interface 4077 can display diagnosis data for example indicating a diagnosis of Impetigo as shown in FIG. 15C. The display of diagnosis data can also include additional information such as treatment instructions, what symptoms to expect, a length of time expected for the abnormality to clear if treatment is applied as instructed, and/or other information. The user can be instructed to receive medical attention in person based on an urgency of the diagnosis data, and one or more local physicians and/or hospitals can be automatically determined by the client device and/or the captured image processing system 4004 based on a determined location of the client device, based on an address of the user in the user's account, and/or based on health insurance information provided by the user. The physicians and/or hospitals can be filtered by specialty based on the diagnosis data, for example, where only dermatologists and/or dermatology facilities are presented to the user in response to the diagnosis data indicating a skin condition that needs medical attention.

The user interface 4077 can present the captured image in conjunction with the diagnosis in a processed and/or unprocessed format. For example, the captured image can be automatically cropped and/or brightness, contrast, and/or other filters may have been automatically applied by the captured image processing system 4004 to better enhance the abnormality in the image. The user interface 4077 can display annotation data overlaid upon the diagnosis data, indicating locations of automatically detected features in the captured image, indicating automatically generated measurements of one or more lesions or other abnormal conditions in the captured image, and/or indicating automatically generated characterization data of the one or more abnormal conditions in the captured image. In embodiments where multiple captured images and/or a video was utilized, a subset of captured image and/or a subset of frames of the video can be displayed, for example as still frames. In some embodiments a change in the abnormality over time can be visually displayed based on displaying corresponding captured images side by side and/or based on displaying multiple measurements taken over time overlaid upon a single image, for example, as discussed in conjunction with the lesion tracking system of FIGS. 16A-16D.

The user interface 4077 can allow the user to elect to transmit the diagnosis data to a designated physician or other user indicated in a user account associated with the user and/or entered by the user via user interface 4077 or other user indicated by the user. The user interface 4077 can allow the user to elect to transmit a prescription automatically generated in the diagnosis data and/or received from a medical professional to a pharmacy indicated by the user via user interface 4077 and/or in the user account. In some embodiments, the diagnosis data can indicate that over the counter medication and/or other commercially available tools and/or devices can be utilized to treat the condition at home. For example, the diagnosis data can indicate that tweezers can be utilized to remove a splinter detected in the captured image and/or can indicate that a salicylic acid toner can be utilized to treat acne detected in the captured image. Links to products corresponding to recommended medication, tools, and/or devices can be provided to the user and/or the user can be prompted to purchase one or more recommended items for home treatment via user interface 4077.

The user interface 4077 can allow the user to elect to generate a formatted report such as PDF report that includes the original and/or processed captured image with or without annotations, and/or that further includes text data generated in the diagnosis data. The user interface 4077 can allow the user to request a second opinion, and the diagnosis data and/or captured image can be transmitted to a medical professional selected automatically and/or selected by the user in response for display to the selected medical professional via user interface features discussed in conjunction with user interface 4076. The user interface 4077 can allow the user to view additional information about the diagnosis, and/or can present links and/or articles to the user for display in via user interface 4077 and/or a web browser. While these features are presented as options to the user in FIG. 15C, some or all of these features can be performed automatically by the client device and/or the captured image processing system 4004 in response to the diagnosis data being generated for the captured image.

FIG. 16A illustrates an embodiment of a lesion tracking system 3002. The lesion tracking system 3002 can receive multiple scans or other longitudinal of the same patient to track changes in one or more lesions detected in the multiple scans over time. In particular, the lesion size, shape, diameter, and/or volume, and/or other characteristics of the lesion such as other abnormality classification data 445 can be determined for each scan, and the changes in these features over time can be measured and tracked. For example, lesions can be determined to shrink, grow, or disappear over subsequent medical scans, and/or new lesions can be detected to appear over subsequent medical scans. Performing such calculations automatically by utilizing the lesion tracking system 3002 can generate more precise measurements than those generated by a radiologist's visual inspection of one or more medical scans. These automated measurements can thus be used to more accurately determine or predict if a patient's condition is bettering or worsening, to more accurately determine or predict if a patient is responding well or poorly to treatment, and/or to otherwise aid in diagnosing a patient's condition.

As shown in FIG. 16A, lesion tracking system 3002 can communicate bi-directionally, via network 150, with the medical scan database 342 and/or other databases of the database storage system 140, with one or more client devices 120, and/or, while not shown in FIG. 16A, one or more subsystems 101 of FIG. 1. In some embodiments, the lesion tracking system 3002 is an additional subsystem 101 of the medical scan processing system 100, implemented by utilizing the subsystem memory device 245, subsystem processing device 235, and/or subsystem network interface 265 of FIG. 2A. In some embodiments, the lesion tracking system 3002 is implemented by utilizing, or otherwise communicates with, the central server 2640. For example, some or all of the databases of the database storage system 140 are populated with de-identified data generated by the medical picture archive integration system 2600. In some embodiments, the lesion tracking system 3002 can receive de-identified medical scans, annotation data, and/or reports directly from the medical picture archive integration system 2600. For example, the lesion tracking system 3002 can request de-identified medical scans, annotation data, and/or reports that match requested criteria, for example, corresponding to training set criteria. In some embodiments, some or all of the lesion tracking system 3002 is implemented by utilizing other subsystems 101 and/or is operable to perform functions or other operations described in conjunction with one or more other subsystems 101.

The lesion tracking system 3002 can be operable to receive, via subsystem network interface 265 or another receiver, a first medical scan that is associated with a first unique patient ID and a first scan date. The lesion tracking system 3002 can also receive a second medical scan that is associated with the first unique patient ID and a second scan date that is different from the first scan date. The first medical scan can include a first plurality of image slices, and the second medical scan can include a second plurality of image slices. As shown in FIG. 16A, the first medical scan and second medical scan can be received as medical scan entries 3005 and 3006, respectively. The medical scan entries can be received from the medical scan database 342, and each entry can include some or all fields of medical scan entries 352 as described in conjunction with FIG. 4A. For example, the unique patient ID can be indicated in the patient identifier data 431 and/or the scan date can be indicated in the scan date data 426. In some embodiments, more than two medical scans of the patient can be received for processing. In some embodiments, medical scan entry 3006 can be received as longitudinal data 433 of medical scan entry 3005 and/or an identifier of medical scan entry 3006 can be determined from longitudinal data 433 of medical scan entry 3005, which can be utilized by the lesion tracking system to fetch medical scan entry 3006 from the medical scan database 342. Medical scan entries 3005 and 3006 can correspond to the same or different scan categories, and can, for example, correspond to the same or different modality.

A lesion detection function 3020 can be performed to detect at least one lesion in medical scan entries 3005 and 3006. In some embodiments, the lesion detection function 3020 is performed on image data 410 on medical scan entries 3005 and 3006 to determine an anatomical location of the lesion, to determine a subset of image slices that contains the lesion for each medical scan, to determine abnormality location data 443 corresponding to the lesion, and/or to otherwise determine the location of the lesion in the image data. For example, as depicted in FIG. 16A, image slice subset 3030 can correspond to the subset of slices that include the detected lesion in image data 410 of medical scan entry 3005, and image slice subset 3031 can correspond to the subset of slices that include the detected lesion in image data 410 of medical scan entry 3006.

In some embodiments, the lesion detection function 3020 is implemented by utilizing a medical scan analysis function, for example, trained by the medical scan image analysis system 112. In such embodiments, the lesion detection function can correspond to the inference step 1354 and/or the detection step 1372 described in conjunction with FIG. 7B, to determine abnormality region 1373. In some embodiments, the lesion is detected in an image slice of the image data 410, A density value, density range and/or other pixel value of pixels determined to correspond to the lesion in the image slice is determined. This density value, density range and/or other pixel value is compared to the value corresponding pixels in neighboring image slices, or pixels within proximity of coordinate values determined to contain the lesion in the image slice. For example, the neighboring image slices can include one or more image slices before or after the image slice in the sequential slice ordering of the image data. If the pixel values compare favorably, this can be utilized to determine that the lesion is included in these neighboring slices and/or to determine which pixels of the neighboring image slices include the lesion. This process can continue for subsequent neighboring image slices to determine the remainder of the image slice subset 3030, continuing until no more neighboring image slices are determined to include the lesion. Thus, the image slice subset 3030 can correspond to a consecutive subset of image slices with respect to the sequential ordering of the image slices of the image data 410.

In some embodiments, the lesion detection function 3020 is first performed on medical scan entry 3005, and the anatomical location and/or subset of image slices is utilized to detect the lesion in medical scan entry 3006, for example, to ensure the same lesion is detected in both medical scan entries and/or to expedite processing of medical scan entry 3006. For example, performing the lesion detection function on medical scan entry 3006 can include searching only a subset of image slices of the medical scan entry 3006 corresponding to and/or neighboring the image slice subset 3030; searching an anatomical region determined in processing medical scan entry 3005 for the lesion; and/or searching only a subset of pixels of some or all image slices corresponding to and/or in proximity to the anatomical region, and/or pixels of the image slice subset 3030 determined to include the lesion. In some embodiments, the lesion detection function includes performing an abnormality similarity function or other medical scan similarity analysis function trained by and/or performed by the medical scan comparison system 116, where a similarity score for lesions detected in medical scan entry 3005 and 3006 is compared to a threshold, and is utilized to determine that the detected in medical scan entry 3006 is the same lesion as that detected in medical scan entry 3005 when the similarity score compares favorably to a threshold.

Once the lesion is detected, the image slice subset 3030, anatomical region data, pixel coordinates corresponding to the detected lesion, and/or other abnormality location data 443 corresponding to the lesion can be utilized as input to one or more lesion measurement functions 3045. In some embodiments, the lesion detection function 3020 is not performed by the lesion tracking system 3002. Instead, abnormality location data 443 that indicates the subset of the image slice subset 3030 and/or 3031, anatomical region data, pixel coordinates corresponding to the detected lesion, and/or other location data can be received from the medical scan database 342 and/or another subsystem 101 for use as input to the lesion measurement function 3045.

The one or more lesion measurement functions 3045 can include a lesion diameter measurement function, as shown in FIG. 16B, to determine diameter measurement 3022 for a lesion 3010 detected in the image data 410 of medical scan entry 3005 and/or to determine a diameter measurement 3024 for the lesion 3010 detected in image data 410 of medical scan entry 3006.

For a lesion 3010 detected in the image data of medical scan entry 3005, the lesion diameter measurement function can include performing a lesion diameter calculation on each of the image slice subset 3030 to generate a set of diameter measurements. Generating the lesion diameter measurement for the lesion of medical scan entry 3005 can include selecting a maximum of the set of diameter measurements. The lesion diameter measurement can correspond to a segment connecting a first point and a second point of a perimeter of the lesion in one of the image slice subset 3030. In some embodiments, the segment is oblique to an x-axis of the one of the image slice subset. In some embodiments, performing the lesion diameter measurement function can include determining a set of pixels of some or all of the subset of image slices that correspond to the perimeter of the first lesion in the one of the first subset of image slices. A set of segment lengths corresponding to a distance between each of a plurality of pairs of pixels can be calculated, for example, where the plurality of pairs of pixels includes every combination of selecting two of the set of pixels. The lesion diameter measurement can be determined by selecting a maximum of the set of segment lengths.

The diameter measurement 3024 corresponding to the diameter of the lesion 3010 in the image data of medical scan entry 3006 can be calculated in the same or different fashion. The diameter measurement 3024 can correspond to a segment on the same image slice index or different image slice index of the image slice that includes the diameter measurement 3022 for medical scan entry 3005. For example, the image slice containing the diameter of the lesion may change depending on how the lesion changed shape over time. Similarly, the axis along which the diameter falls relative to a coordinate system of the image slices can be different for diameter measurements 3022 and 3024, as shown in FIG. 16B.

In some embodiments, the diameter measurement can be measured across multiple slices, for example, based upon the three-dimensional structure of the lesion. For example, segment lengths for a plurality of pairs of pixels corresponding to the three-dimensional surface of the lesion across some or all of the image slice subset 3030 can be utilized to compute the diameter measurement 3022. In particular, a slice thickness can be determined, for example, based on metadata of the medical scan entry 3005 and/or based on the modality of the medical scan entry 3005, and can be used in computing the segment lengths for each of the plurality of pairs. The maximum segment length can be utilized as the diameter measurement 3022.

In some embodiments, the one or more lesion measurement functions 3045 can include a lesion area measurement function. For example, based on pixels in each of the subset of image slices determined to be included in the lesion, an area can be computed. In particular, a fixed pixel area corresponding to the true area represented by each individual pixel can be determined, for example, in the medical scan entry metadata and/or based on the modality of the medical scan. This pixel area can be multiplied by the number of pixels determined to be included in the lesion to calculate a lesion area for each image slice in the image slice subset.

Furthermore, this calculated set of areas can be utilized to calculate a volume approximation of the lesion by performing a lesion measurement functions 3045 corresponding to a lesion volume measurement function. Performing the lesion volume measurement function can include performing a Riemann sum calculation on the set of lesion area measurements, where a uniform partition width of the Riemann sum is determined based on the determined slice thickness of the image slices in the image data. For example, every pair of consecutive image slices of the image slice subset 3030 can correspond to one of a plurality of trapezoidal areas. Performing the performing the lesion volume calculation can include performing a summation of the plurality of trapezoidal areas. Each of the plurality of trapezoidal areas can be calculated by multiplying the slice thickness by half of the sum of a first base and a second base, where a value of the first base is equal to a first one of the set of lesion area measurements corresponding to a first one of a corresponding pair of consecutive image slices, and where a value of the second base is equal to a second one of the of the set of lesion area measurements corresponding to a second one of the corresponding pair of consecutive image slices.

FIG. 16C illustrates an example of performing the lesion volume measurement function. Image slice subset 3030 is determined from the image data 410 based on the detection of lesion 3010, and includes slice indexes 0-10. The lesion area of lesion 3010 can be calculated for each image slice, as illustrated in the discrete plot 3032 of slice index vs lesion area. Plot 3032 can be utilized to determine volume as the area under the curve of plot 3034 to perform a trapezoidal Riemann sum approximation of lesion volume, where the x-axis measures cross-sectional distance, or width, from slice 0. This can be determined by multiplying the slice index of the x-axis of plot 3032 by the slice thickness to determine the x-value of each of the coordinates plotted in plot 3032. A continuous curve of lesion area can be approximated by connecting discrete points of plot 3032 to create the curve of plot 3034. While linear segments are shown to connect the discrete points in FIG. 16C, any curve fitting function can be utilized to generate the area curve. In this example, calculating the area under the curve to approximate volume can correspond to a trapezoidal Riemann sum approximation, but other Riemann sum approximations, other integral approximation functions, and/or other volume approximation techniques can be utilized to approximate volume based on the discrete areas of plot 3032.

One or more of the lesion measurement functions 3045 can be medical scan analysis functions, for example, trained by and/or performed by the medical scan image analysis system 112 and/or trained and/or performed in the same fashion as other medical scan analysis functions described herein. In some embodiments, the lesion measurement function is implemented by utilizing the abnormality classification step 1374 to generate classification data 1375 that includes the lesion measurement data 3040 and/or 3041.

The lesion measurements can be compared by performing a lesion measurement change function 3050 on the lesion measurement data 3040 and 3041. The lesion measurement change function 3050 can include computing difference of corresponding measurement values, such as a difference in diameter and/or a difference in volume of the lesion. The lesion measurement function can also calculate a Euclidean distance of vectors that include a set of measurements in lesion measurement data 3040 and 3041. The lesion measurement change function 3050 can be a medical scan analysis function, such as a medical scan comparison function, trained by and/or performed by the medical scan image analysis system 112, trained by and/or performed by the medical scan comparison system 116, and/or trained and/or performed in the same fashion as other medical scan analysis functions described herein.

In some embodiments, the lesion measurement function 3045 is not performed by the lesion tracking system 3002. Instead, abnormality classification data 445 corresponding to one or more measurement categories 444 can include lesion measurement data 3040 and/or 3041, and can be received from the medical scan database 342 and/or another subsystem 101 for use as input to the lesion measurement change function 3050.

The lesion measurement change data 3055 can be transmitted via subsystem network interface 265 and/or via another transmitter, for transmission to one or more client devices 120 for display via a display device. For example, the lesion measurement change data can be displayed as text and/or can be displayed visually in conjunction with the image data 410 of medical scan entries 3005 and/or 3006 by utilizing the medical scan assisted review system 102. For example, the measurement data can be displayed as state change data of abnormalities detected in longitudinal data as described in conjunction with the of the medical scan assisted review system 102. Alternatively or in addition, the lesion measurement change data 3055 can be sent to one or more other subsystems for processing, for example, to be utilized as training data by one or more medical scan analysis functions trained by medical scan image analysis system 112. Alternatively or in addition, the lesion measurement change data 3055 can be sent to the medical scan database for storage, for example, as part of the longitudinal data 433 for medical scan entry 3005 and/or 3006. Alternatively or in addition, the lesion measurement data 3040 and/or 3041 can be sent to the medical scan database for storage, for example, as part of abnormality classification data 445 for medical scan entry 3005 and/or 3006, respectively, corresponding to abnormality classifier categories 444 corresponding to a diameter category, an area category, a volume category, or other measurement category.

In some embodiments, a set of three or more medical scans of the same patient are received, and the lesion measurement change data is calculated for consecutive ones of the set of three or more medical scans with respect to scan data. In some embodiments, lesion measurement change data is also calculated for some or all of every possible pair of the medical scans in the set of three or more medical scans.

FIG. 16D illustrates an example of an interface 3080, which can be displayed on a display device of client device 120. The interface can present a selected image slice of each image slice subset 3030 and 3031. A region detected to include the lesion can be overlaid on the image slice as annotation data, and/or other annotation data can be displayed to indicate the lesion. In some embodiments, the diameter measurement data can be displayed visually for medical scan entries 3005 and/or 3006. For example, the image slice of image slice subset 3030 and/or 3031 determined to include the largest diameter can be automatically presented, and a segment connecting the corresponding first pixel and second pixel determined to correspond to endpoints of the diameter can be automatically overlaid on the displayed image slice. In some embodiments, a solid or semi-transparent outline and/or shading of the pixels determined to include the lesion in an image slice of medical scan entry 3005 can be overlaid upon the corresponding pixel coordinates in the display of the corresponding image slice of medical scan entry 3006 by the interface, for example, to visually depict how much the lesion has shrunk, grown, or otherwise changed shape and/or position. In some embodiments, some or all of the lesion measurement data and/or lesion measurement change data is displayed as text in conjunction with the image data. In some embodiments, a three-dimensional rendering of the lesion, generated based on the lesion volume measurement data, can be displayed in accordance with a three-dimensional visualization interface.

In some embodiments, other classification data can be generated based on a diameter measurement, area measurement, and/or volume measurement of the lesion measurement data. For example, the lesion diameter data can be utilized to determine RECIST eligibility data and/or can be utilized to determine whether or not the lesion corresponds to a target lesion or non-target lesion. The lesion change measurement data can be utilized to determine RECIST evaluation data based on the change in the lesion in a more recent scan when compared to a prior scan. In particular, the lesion change measurement data can be utilized to indicate if the lesion is “Complete Response”, “Partial Response”, “Stable Disease”, or “Progressive Disease”. In cases where three or more scans are evaluated for a patient, the RECIST evaluation data can reflect changes over time. In some embodiments, a plurality of lesions are detected, measured and tracked in the medical scan entries 3005 and 3006. RECIST eligibility data and/or RECIST evaluation data can be generated for each the plurality of lesions, and/or RECIST evaluation data and/or diagnosis data can be generated based on assessing the plurality of lesions as a whole.

RECIST eligibility data and/or evaluation data can be transmitted to the client device for display via the display device, can be transmitted to the medical scan database for storage in a corresponding medical scan entry as abnormality annotation data 442 and/or as longitudinal data 433, and/or can be transmitted to other subsystems 101, for example, as part of a training set to train a medical scan analysis function. Other standardized medical assessment scores characterizing the lesion, such as a Lung-RADS assessment score, can be generated automatically based on the measurement data.

The medical scan entries 3005 and 3006 can be received at the same time or different times for processing. For example, as medical scan entries 3005 and 3006 correspond to different scan dates, they can be sent to the medical scan lesion tracking system for processing as scans are taken for the patient. In some embodiments, only medical scan entry 3005 is received, and lesion measurement data is calculated for medical scan entry 3005. This can be sent to the client device 120 and/or can be sent to the medical scan database 342 for storage as abnormality annotation data 442 or other data of the medical scan entry 3005. Later, medical scan entry 3006 can be received, and lesion location data and/or lesion measurement data 3040 corresponding to the lesion in medical scan entry 3005 can be fetched from the database in response to generate the lesion measurement change data 3055. The lesion location and/or measurement data of the lesion in medical scan entry 3005 can also be utilized to aid in detecting the lesion in medical scan entry 3006, to aid in generating lesion measurement data for the lesion in medical scan entry 3006.

In some embodiments, the data generated by the lesion tracking system 3002 can be utilized to train a longitudinal lesion model. The longitudinal lesion model can be generated by the lesion tracking model, and/or output of the lesion tracking model can be sent to another subsystem, such as the medical scan image analysis system. For example, a training step 1352 can be performed on a plurality of sets of longitudinal data, where each set of longitudinal data corresponds to a patient and includes the lesion measurement data, the lesion measurement change data, the classification data such as RECIST eligibility data, RECIST evaluation data, and/or Lung-RADS assessment data determined for a corresponding plurality of medical scans entries of the patient. Each of the plurality of sets of longitudinal data can include other fields of the corresponding plurality of medical scan entries of the patient, such as the image data, diagnosis data, patient history, and/or other relevant fields of one or more medical scan entries of the corresponding patient.

The longitudinal lesion model can be utilized to perform an inference function on subsequent medical scans, such as a single medical scan entry of a new patient or a set of medical scan entries of a new patient. The inference function can be performed by the lesion tracking system 3002, by the medical scan image analysis system 112, and/or by another subsystem 101. The inference function corresponding to the longitudinal lesion model can be a medical scan analysis function, and can be trained and/or performed as discussed herein with regards to medical scan analysis function.

By performing the inference function on one or more medical scans of a patient, lesion change prediction data can be generated for at least one lesion detected in the one or more medical scans. For example, the lesion change prediction data can include a lesion growth factor or a lesion shrinkage factor. Alternatively or in addition, the inference function can generate other inference data, such as other assessment and/or prediction data. This can include inference data that assesses lesion growth and/or shrinkage in the set of medical scans, that assesses and/or predicts changes in the severity of the patient's condition, that diagnoses the new patient, that includes determined treatment steps for the new patient, that determines whether the new patient is responding favorably or unfavorably to treatment, and/or that otherwise assesses and/or predicts the new patient's current condition and/or future condition. Some or all of the inference data generated by performing the inference function can be determined based on assessing the size and/or characteristics of detected lesions, and/or based on predicting the change in size or change in characteristics of detected lesions.

In some embodiments, performing the inference function includes performing the lesion measurement function on the one or more medical scans of the new patient and/or includes performing the lesion measurement change function on the one or more medical scans of the new patient. The lesion measurement data and/or lesion measurement change data generated for the new patient can be input to the inference function in addition to or instead of the one or more medical scans entries themselves.

The lesion change prediction data or other inference data can be transmitted to a client device for display on a display device via an interface, for example, in conjunction with the one or more medical scans of the new patient. Presenting the lesion change prediction data can include overlaying a predicted diameter, area, and/or volume change of the lesion, for example, by displaying a solid or semi-transparent outline and/or shading of the pixels in accordance with a predicted future size, a predicted future shape, and/or predicted future location of the lesion in at least one image slice of the one or more new medical scan entries, to visually depict how much the lesion is predicted to shrink, grow, or otherwise change shape and/or position. In some embodiments, a predicted future three-dimensional rendering of the lesion can be displayed in accordance with a three-dimensional visualization interface.

In some embodiments, the inference function can generate a set of lesion change prediction data corresponding to a set of different projected time spans. For example, lesion change prediction data can be generated for one year, two years, and three years in the future, and the prediction data for each projected time span can be sent to the client device for display. In some embodiments, the interface can prompt the user to select one of the set of different projected time spans, and the prediction data for the selected one of the projected time spans will be displayed accordingly. To enable this capability, the longitudinal lesion model can be trained on sets of longitudinal data with medical scans of varying time spans, and the relative time between dates of medical scans and/or dates of other data in a set of longitudinal data can be utilized in performing the training step.

In some embodiments, before execution of the inference function on the one or more medical scans of the new patient, a user interacting with the interface displayed by the display device can select a projected time span from a discrete set of options, and/or can enter any projected time span. The inference function can be performed by utilizing the selected projected time span received from the client device, and prediction data can reflect this selected projected time span from the current date and/or from a date of the most recent scan in the one or more medical scans for the new patient. For example, if the selected projected time span is 18 months, the inference data can include a lesion growth factor, a lesion shrinkage factor, and/or other prediction data projected for 18 months in the future.

In some embodiments, medical scan entry 3005 and/or medical scan entry 3006 already have associated measurement data. Human assessment data, such as human measurement data corresponding to a radiologist measurement or other human measurement of the lesion, can be included in the medical scan entry and/or can be received in conjunction with the medical scan entry. For example, a human diameter measurement can be included in the human assessment data of a medical scan corresponding to a radiologist's documentation of the diameter based on visual inspection of the image data of the medical scan. This human assessment data can correspond to abnormality annotation data 442 with diagnosis author data 450 corresponding to the radiologist or other human that took the measurement. This diagnosis author data 450 can correspond to an identifier of the radiologist or other human in a corresponding user profile entry 354 the user database 344. The human assessment data can also include abnormality classification data 445, such as RECIST eligibility data, RECIST evaluation data, a Lung-RADS assessment score, or other abnormality classification data 445 discussed herein.

Performing one or more of the lesion measurement functions on the medical scan entry 3005 and/or 3006 can be further utilized to measure the accuracy of the human assessment data taken by a radiologist. For example, a radiologist may have measured a diameter incorrectly by failing to measure the distance between two points of the perimeter of the lesion properly, by identifying a wrong segment on an image slice as being the maximum segment connecting perimeter points of the lesion, by identifying a maximum segment in an image slice when a different image slice includes a portion of the lesion with a larger maximum segment, by considering pixels of an image slice that are not part of the lesion or do not correspond to the perimeter of the lesion when determining the diameter, by failing to consider a true diameter that connects two points along the surface of a three-dimensional representation of the lesion where the two points are on different image slices of the medical scan, by mischaracterizing the scan and taking a measurement for a lesion that is not actually a lesion, by mischaracterizing the scan and failing to take a measurement for a lesion based on a determination that the lesion did not exist or based on a determination that the lesion does not meet criteria such as RECIST criteria, by characterizing a lesion as a target lesion or non-target lesion improperly, by characterizing a lesion or the medical scan as “Complete Response”, “Partial Response”, “Stable Disease”, or “Progressive Disease” improperly, by determining abnormality classification data 445 incorrectly, by otherwise measuring and/or characterizing the lesion improperly, and/or by otherwise measuring and/or characterizing a change in the lesion across multiple medical scans of the patient improperly.

The accuracy of human assessment data can be determined by generating automated assessment data. The automated assessment data can be generated by performing the lesion detection function, by performing the one or more lesion measurement functions, and/or by classifying the lesion, for example, by performing abnormality classification step 1374. The lesion location determined in the detection data, the lesion diameter, area and/or volume determined in the lesion measurement data, and/or abnormality classification data 445 for one or more abnormality classifier categories 444 can be compared to corresponding portions of the human assessment data by performing a similarity function, by computing a difference in values, by determining whether or not the values match or otherwise compare favorably, and/or by computing a Euclidean distance between feature vectors of the human assessment data and the automated assessment data.

The difference between some or all of the human assessment data and the automated assessment data can be compared to a threshold to determine if the human assessment data is correct or incorrect. The difference between some or all of the human assessment data and the automated assessment data can also correspond to accuracy data such as an accuracy score, and the accuracy score can be assigned to the corresponding radiologist or other human. For example, the accuracy score can be mapped to the radiologist in the corresponding user profile entry 354 of the user database 344. The accuracy score can also be transmitted to a client device for display via the display device. Accuracy scores that compare unfavorably to a threshold can be utilized to automatically flag radiologists or other humans that recorded an incorrect measurement or characterization of a lesion, and/or are consistently recording incorrect measurements or characterizations of lesions.

As may be used herein, the terms “substantially” and “approximately” provides an industry-accepted tolerance for its corresponding term and/or relativity between items. Such an industry-accepted tolerance ranges from less than one percent to fifty percent and corresponds to, but is not limited to, component values, integrated circuit process variations, temperature variations, rise and fall times, and/or thermal noise. Such relativity between items ranges from a difference of a few percent to magnitude differences. As may also be used herein, the term(s) “configured to”, “operably coupled to”, “coupled to”, and/or “coupling” includes direct coupling between items and/or indirect coupling between items via an intervening item (e.g., an item includes, but is not limited to, a component, an element, a circuit, and/or a module) where, for an example of indirect coupling, the intervening item does not modify the information of a signal but may adjust its current level, voltage level, and/or power level. As may further be used herein, inferred coupling (i.e., where one element is coupled to another element by inference) includes direct and indirect coupling between two items in the same manner as “coupled to”. As may even further be used herein, the term “configured to”, “operable to”, “coupled to”, or “operably coupled to” indicates that an item includes one or more of power connections, input(s), output(s), etc., to perform, when activated, one or more its corresponding functions and may further include inferred coupling to one or more other items. As may further be used herein, the term “associated with”, includes direct and/or indirect coupling of separate items and/or one item being embedded within another item. As may still further be used herein, the term “automatically” refers to an action caused directly by a processor of a computer network in response to a triggering event and particularly without human interaction.

As may be used herein, the term “compares favorably”, indicates that a comparison between two or more items, signals, etc., provides a desired relationship. For example, when the desired relationship is that signal 1 has a greater magnitude than signal 2, a favorable comparison may be achieved when the magnitude of signal 1 is greater than that of signal 2 or when the magnitude of signal 2 is less than that of signal 1. As may be used herein, the term “compares unfavorably”, indicates that a comparison between two or more items, signals, etc., fails to provide the desired relationship.

As may also be used herein, the terms “processing module”, “processing circuit”, “processor”, “processing device” and/or “processing unit” may be a single processing device or a plurality of processing devices. Such a processing device may be a microprocessor, micro-controller, digital signal processor, graphics processing unit, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions. The processing module, module, processing circuit, and/or processing unit may be, or further include, memory and/or an integrated memory element, which may be a single memory device, a plurality of memory devices, and/or embedded circuitry of another processing module, module, processing circuit, and/or processing unit. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that if the processing module, module, processing circuit, and/or processing unit includes more than one processing device, the processing devices may be centrally located (e.g., directly coupled together via a wired and/or wireless bus structure) or may be distributedly located (e.g., cloud computing via indirect coupling via a local area network and/or a wide area network). Further note that if the processing module, module, processing circuit, and/or processing unit implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory and/or memory element storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry. Still further note that, the memory element may store, and the processing module, module, processing circuit, and/or processing unit executes, hard coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated in one or more of the Figures and/or described herein. Such a memory device or memory element can be included in an article of manufacture. While the processing module, module, processing circuit, and/or processing unit device may be a general purpose computing device, the execution of the hard coded and/or operational instructions by the processing module, module, processing circuit, and/or processing unit configures such a general purpose computing device as a special purpose computing device to implement the corresponding steps and/or functions illustrated in one or more of the Figures and/or described herein. In particular, the hard coded and/or operational instructions by the processing module, module, processing circuit, and/or processing unit implement acts and algorithms performed by the processing module, module, processing circuit, and/or processing unit. Such acts and algorithms can be identified by name, can be illustrated via flowchart and/or described in words.

One or more embodiments have been described above with the aid of method steps illustrating the performance of specified functions and relationships thereof. The boundaries and sequence of these functional building blocks and method steps have been arbitrarily defined herein for convenience of description. Alternate boundaries and sequences can be defined so long as the specified functions and relationships are appropriately performed. Any such alternate boundaries or sequences are thus within the scope and spirit of the claims. Further, the boundaries of these functional building blocks have been arbitrarily defined for convenience of description. Alternate boundaries could be defined as long as the certain significant functions are appropriately performed. Similarly, flow diagram blocks may also have been arbitrarily defined herein to illustrate certain significant functionality.

To the extent used, the flow diagram block boundaries and sequence could have been defined otherwise and still perform the certain significant functionality. Such alternate definitions of both functional building blocks and flow diagram blocks and sequences are thus within the scope and spirit of the claims. One of average skill in the art will also recognize that the functional building blocks, and other illustrative blocks, modules and components herein, can be implemented as illustrated or by discrete components, application specific integrated circuits, processors executing appropriate software and the like or any combination thereof.

In addition, a flow diagram may include a “start” and/or “continue” indication. The “start” and “continue” indications reflect that the steps presented can optionally be incorporated in or otherwise used in conjunction with other routines. In this context, “start” indicates the beginning of the first step presented and may be preceded by other activities not specifically shown. Further, the “continue” indication reflects that the steps presented may be performed multiple times and/or may be succeeded by other activities not specifically shown. Further, while a flow diagram indicates a particular ordering of steps, other orderings are likewise possible provided that the principles of causality are maintained.

The one or more embodiments are used herein to illustrate one or more aspects, one or more features, one or more concepts, and/or one or more examples. A physical embodiment of an apparatus, an article of manufacture, a machine, and/or of a process may include one or more of the aspects, features, concepts, examples, etc. described with reference to one or more of the embodiments discussed herein. Further, from figure to figure, the embodiments may incorporate the same or similarly named functions, steps, modules, etc. that may use the same or different reference numbers and, as such, the functions, steps, modules, etc. may be the same or similar functions, steps, modules, etc. or different ones.

The term “system” is used in the description of one or more of the embodiments. A system implements one or more functions via a device such as a processor or other processing device or other hardware that may include or operate in association with a memory that stores operational instructions. A system may operate independently and/or in conjunction with software and/or firmware. As also used herein, a system may contain one or more sub-system, each of which may be one or more systems.

As may further be used herein, a computer readable memory includes one or more memory elements. A memory element may be a separate memory device, multiple memory devices, or a set of memory locations within a memory device. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. The memory device may be in a form a solid state memory, a hard drive memory, cloud memory, thumb drive, server memory, computing device memory, and/or other physical medium for storing digital information.

While particular combinations of various functions and features of the one or more embodiments have been expressly described herein, other combinations of these features and functions are likewise possible. The present disclosure is not limited by the particular examples disclosed herein and expressly incorporates these other combinations. 

What is claimed is:
 1. An electrocardiogram (ECG) interpretation system, comprising: at least one processor; and a memory that stores operational instructions that, when executed by the at least one processor, cause the ECG interpretation system to: perform a waveform detection function on a captured image of an ECG printout to determine a plurality of locations of a plurality of ECG waveforms in the captured image; generate a plurality of waveform images by partitioning the captured image based on the plurality of locations, wherein each of the plurality of waveform images includes one of the plurality of ECG waveforms; generate a plurality of pseudo-raw ECG signal data by performing a signal reconstruction function on each of the plurality of waveform images, wherein each of the plurality of pseudo-raw ECG signal data corresponds to one of the plurality of waveform images; and generate diagnosis data, for displayed by a display device of a client device, by performing a diagnosing function on the plurality of pseudo-raw ECG signal data.
 2. The ECG interpretation system of claim 1, wherein the ECG printout was generated by an ECG machine based on electrical activity recorded by the ECG machine, and wherein the captured image was generated by a utilizing an image capture device to generate the captured image from the ECG printout.
 3. The ECG interpretation system of claim 2, wherein the client device corresponds to a mobile device, wherein the image capture device corresponds to a camera, wherein the camera is coupled to the mobile device, wherein the captured image is transmitted to the ECG interpretation system by the mobile device.
 4. The ECG interpretation system of claim 2, wherein the image capture device corresponds to a scanner.
 5. The ECG interpretation system of claim 1, wherein the waveform detection function utilizes a computer vision model trained on a training set of waveform images.
 6. The ECG interpretation system of claim 1, wherein the waveform detection function utilizes standardized layout information, wherein the standardized layout information indicates relative positions of waveforms in standard ECG printouts.
 7. The ECG interpretation system of claim 6, wherein the standardized layout information indicates relative locations of exactly twelve waveforms, wherein each of the exactly twelve waveforms corresponds to one of twelve ECG leads, and wherein the plurality of waveform images includes exactly twelve waveform images corresponding to the twelve ECG leads.
 8. The ECG interpretation system of claim 1, wherein the waveform detection function utilizes standardized formatting feature information, wherein the standardized formatting feature information indicates at least one relative position of at least one additional feature in standard ECG printouts, and wherein the performing the waveform detection function includes detecting the at least one additional feature in the ECG printout.
 9. The ECG interpretation system of claim 1, wherein the signal reconstruction function determines a plurality of discrete points for one of the plurality of waveform images, and wherein a corresponding one of the plurality of pseudo-raw ECG signal data includes the plurality of discrete points, wherein the diagnosing function is trained on a training set of raw ECG signal data, and wherein each raw ECG signal data in the training set includes discrete points characterizing the raw ECG signal data.
 10. The ECG interpretation system of claim 1, wherein performing the diagnosing function on the plurality of pseudo-raw ECG signal data includes: generating twelve sub-diagnosis data, wherein each of the twelve sub-diagnosis data is generated by performing one of twelve inference functions on a corresponding one of twelve pseudo-raw ECG signal data, wherein each of the twelve inference functions corresponds to one of twelve ECG leads and is trained on a training set of raw ECG signal data for the corresponding one of the twelve ECG leads; and performing a final inference function on the twelve sub-diagnosis data to generate the diagnosis data.
 11. The ECG interpretation system of claim 1, wherein the captured image is received from the client device, wherein the ECG printout corresponds to a patient, and wherein the client device is associated with the patient.
 12. The ECG interpretation system of claim 1, wherein the captured image is received from the client device, wherein the ECG printout corresponds to a patient, and wherein the client device is associated with a medical professional responsible for the patient.
 13. The ECG interpretation system of claim 1, wherein the ECG printout is received in an first email transmission from a first email address associated with a requestor to a second email address associated with the ECG interpretation system, wherein the diagnosis data is transmitted in a second email transmission from the second email address to the first email address, and wherein the requestor is a user of the client device.
 14. The ECG interpretation system of claim 13, wherein the second email transmission includes a document for display to the requestor via the client device, and wherein the document includes the diagnosis data and further includes the plurality of pseudo-raw ECG signal data.
 15. The ECG interpretation system of claim 1, wherein the diagnosis data is displayed via the display device in conjunction with the captured image.
 16. The ECG interpretation system of claim 1, wherein the diagnosis data is displayed via the display device in conjunction with the plurality of pseudo-raw ECG signal data via a user interface.
 17. The ECG interpretation system of claim 16, wherein the diagnosis data indicates at least one abnormality in at least one of the plurality of pseudo-raw ECG signal data, and wherein the at least one abnormality is visually indicated in the display of the at least one of the plurality of pseudo-raw ECG signal data.
 18. The ECG interpretation system of claim 17, wherein the operational instructions, when executed by the at least one processor, further cause the ECG interpretation system to: generating normal pseudo-raw ECG signal data by removing the at least one abnormality from the at least one of the plurality of pseudo-raw ECG signal data, wherein the normal pseudo-raw ECG signal data is displayed via the display device in conjunction with the diagnosis data and the plurality of pseudo-raw ECG signal data.
 19. The ECG interpretation system of claim 1, wherein the operational instructions, when executed by the at least one processor, further cause the ECG interpretation system to: receive a second captured image of a patient's skin; generate second diagnosis data by performing a second diagnosing function on the second captured image, wherein the second diagnosing function utilizes a computer vision model trained on a plurality of images of skin corresponding to a plurality of skin conditions; and transmit second diagnosis data to a second client device for display via a second display device.
 20. A method for execution by an ECG interpretation system, the method comprising: performing a waveform detection function on a captured image of an ECG printout to determine a plurality of locations of a plurality of ECG waveforms in the captured image; generating a plurality of waveform images by partitioning the captured image based on the plurality of locations, wherein each of the plurality of waveform images includes one of the plurality of ECG waveforms; generating a plurality of pseudo-raw ECG signal data by performing a signal reconstruction function on each of the plurality of waveform images, wherein each of the plurality of pseudo-raw ECG signal data corresponds to one of the plurality of waveform images; and generating diagnosis data, for displayed by a display device of a client device, by performing a diagnosing function on the plurality of pseudo-raw ECG signal data. 